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 1051-1075 of 1657 flagged pages
Storage Develop for Azure Files with .NET ...icles/storage/files/storage-dotnet-how-to-use-files.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides both Windows and Linux mounting guidance via links, but all direct code examples for System.IO usage assume a Windows-style SMB mount (e.g., Z:\file-share) and do not show Linux/macOS equivalents (such as /mnt/file-share). Windows paths are used exclusively in all sample code, and there are no examples or notes for Linux/macOS users on how to adapt these code samples for their platforms. The mounting section references Linux, but the actual .NET code is Windows-centric.
Recommendations
  • Add explicit Linux/macOS code examples using POSIX-style paths (e.g., '/mnt/file-share') alongside Windows examples.
  • Include a note or section explaining how to adapt System.IO code for Linux/macOS, clarifying that the path format and mount point differ.
  • Show how to mount Azure Files on Linux/macOS and reference the resulting mount path in code samples.
  • Where examples use Windows drive letters, provide equivalent Linux/macOS examples (e.g., using '/mnt/azurefiles').
  • Ensure parity in example ordering: present Windows and Linux/macOS examples side-by-side or alternate which comes first.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation focuses on SMB Azure file shares and authorization, with a clear emphasis on Windows concepts such as Windows ACLs and Windows tools like robocopy. Only Windows ACLs are mentioned for directory/file-level permissions, and the example tool for copying ACLs is robocopy, which is Windows-specific. There is no mention of Linux/macOS equivalents for ACLs or file transfer tools, nor any guidance for non-Windows environments.
Recommendations
  • Clarify whether Azure Files supports POSIX ACLs for NFS shares or Linux clients, and if so, provide documentation or links.
  • Include examples or guidance for copying data and preserving ACLs from Linux/macOS systems, such as using rsync, cp --preserve, or Azure CLI/REST API.
  • Mention any limitations or differences in ACL support for non-Windows clients.
  • If Windows ACLs are the only supported model for SMB Azure file shares, explicitly state this to set expectations for Linux/macOS users.
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-14 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 provides many examples and instructions that are Windows-centric, such as registry edits, PowerShell commands, and references to Windows File Explorer and Windows-specific attributes. Windows tools and workflows (cmd, PowerShell, File Explorer, registry edits) are described in detail, while Linux/macOS equivalents are rarely mentioned or omitted. NFS and Linux tools are referenced only in the NFS section, and there are few concrete Linux/macOS examples for common tasks like credential management, ACLs, or troubleshooting.
Recommendations
  • Add Linux/macOS equivalents for credential management, file attribute inspection, and ACL management (e.g., using mount, smbclient, getfacl/setfacl, etc.).
  • Provide examples for mounting/unmounting Azure Files shares on Linux/macOS, including troubleshooting steps.
  • Include Linux/macOS commands for inspecting alternate data streams (if relevant) or clarify their absence.
  • Where PowerShell or Windows registry edits are described, note that these steps are Windows-only and provide guidance for Linux/macOS users if possible.
  • Balance the order of examples so that Linux/macOS instructions are presented alongside or before Windows instructions where applicable.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias by repeatedly referencing Windows access control lists (ACLs) as the mechanism for directory and file-level permissions, and by using terminology and migration tools (e.g., PowerShell cmdlet for migrating SMB share permissions) that are specific to Windows environments. Windows ACLs are mentioned as the only supported method for granular permissions, and the documentation analogizes Azure RBAC roles to Windows file server ACLs. However, the actual share-level permission assignment is cross-platform via Azure Portal, PowerShell, and CLI, and the examples for PowerShell and CLI are provided in parallel. There are no Linux/macOS-specific examples or discussion of non-Windows ACLs, which may create friction for non-Windows users.
Recommendations
  • Clarify whether directory and file-level permissions can be managed from Linux/macOS clients, and if not, explicitly state this limitation.
  • If possible, provide guidance or references for managing Azure Files permissions from Linux/macOS clients, or explain the platform limitations.
  • Add a note about cross-platform compatibility for Azure CLI and Portal steps, and clarify any Windows-specific requirements for PowerShell or ACL management.
  • Consider including examples or discussion relevant to Linux/macOS administrators, such as mounting Azure Files shares on those platforms and the implications for permissions.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page is primarily focused on enabling Microsoft Entra Domain Services authentication for Azure Files over SMB, which is a feature that is most commonly used in Windows environments. While the page does mention Linux VM support and provides a link to Linux-specific instructions, the majority of examples, especially for configuring Kerberos encryption, use Windows PowerShell cmdlets and Windows-centric tooling. The instructions for enabling AES-256 encryption are exclusively for Windows Server Active Directory PowerShell and require a Windows domain-joined client. Windows/PowerShell examples are presented first and in more detail, with Linux equivalents referenced only via external links.
Recommendations
  • Add explicit Linux command-line examples (e.g., using Azure CLI, shell scripts, or Linux-native tools) for steps where possible, especially for storage account configuration.
  • Provide guidance or links for configuring Kerberos encryption types for storage accounts from Linux domain-joined machines, if supported.
  • Where Windows PowerShell is required, clarify if there are any Linux alternatives or explicitly state that these steps are Windows-only.
  • Ensure Linux documentation is equally discoverable and referenced in relevant sections, not just as a side note.
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-14 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 for configuring DNS forwarding for Azure Files is heavily oriented towards Windows environments. All code examples use PowerShell cmdlets specific to Windows DNS Server, and there are no equivalent instructions or examples for Linux-based DNS servers (such as BIND or dnsmasq). The prerequisites mention Azure PowerShell, and the workflow assumes familiarity with Windows DNS tools. While the text notes that 'all of the steps described here are possible with any DNS server, not just the Windows DNS Server,' no guidance or examples are provided for Linux or cross-platform scenarios.
Recommendations
  • Add step-by-step instructions and configuration examples for popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound), including how to set up conditional forwarding for the relevant Azure endpoints.
  • Provide equivalent command-line examples using Linux tools (e.g., dig, nsupdate) for testing DNS resolution and cache clearing.
  • Clarify any differences in DNS forwarding setup between Windows and Linux environments, especially for organizations using mixed infrastructure.
  • Reorder or parallelize examples so that Linux and Windows instructions are presented side-by-side or in separate sections, rather than Windows-first.
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-14 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 migrating to SMB Azure file shares demonstrates a moderate Windows bias. Windows tools (RoboCopy, Storage Migration Service, Azure File Sync) are described in detail and recommended prominently, with examples and guidance focused on Windows environments. Linux migration scenarios are acknowledged but receive less coverage, with only Azure Storage Mover suggested and no Linux-specific migration examples or tool guidance. Windows migration patterns and tools are presented first and in greater detail, while Linux options are limited and less explained.
Recommendations
  • Add Linux-specific migration examples, such as using smbclient, rsync, or other Linux-native tools to copy SMB shares to Azure file shares.
  • Provide step-by-step guidance for mounting Azure file shares on Linux and performing file migrations, including preserving metadata and ACLs where possible.
  • Include a comparison table of Windows and Linux migration tools, highlighting their capabilities and limitations for Azure file share migrations.
  • Ensure that Linux migration scenarios are described with equal detail and clarity as Windows scenarios, including troubleshooting and best practices.
  • Reference third-party or open-source Linux tools where appropriate, and clarify any limitations in file fidelity or ACL preservation.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides several examples and instructions using Windows-centric tools and patterns, such as PowerShell cmdlets (Resolve-DnsName), and references to Windows features (SMB over QUIC, Azure File Sync on Windows Server). While Linux is mentioned in some contexts (e.g., nslookup), most examples and tooling guidance are Windows-first or Windows-only, and PowerShell is presented as the primary example for DNS resolution. There is also a reliance on Windows terminology and features, with Linux alternatives mentioned but not given equal prominence or example detail.
Recommendations
  • Provide equivalent Linux/macOS command examples alongside PowerShell (e.g., show 'dig' and 'nslookup' usage for DNS resolution).
  • When referencing tooling or configuration steps, include both Windows and Linux/macOS instructions where possible.
  • Ensure that Linux-specific networking patterns (such as mounting NFS shares, configuring DNS, or VPN clients) are documented with the same depth as Windows examples.
  • Where PowerShell scripts are provided for automation, offer Bash or Python alternatives for Linux/macOS users.
  • Clarify when features or steps are Windows-only, and provide links or guidance for Linux/macOS alternatives if available.
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-14 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 provides parity for both Windows and Linux users in most areas, especially for core snapshot management tasks (create, list, delete) via Azure Portal, PowerShell, and CLI. However, there is a notable Windows-first bias in sections describing how to restore from SMB file share snapshots: Windows workflows (File Explorer, Previous Versions tab, Robocopy) are described in detail, while Linux equivalents are only briefly covered and lack depth (e.g., no example of restoring individual files from a mounted SMB snapshot on Linux). Windows-specific tools (Robocopy, File Explorer) are mentioned exclusively, and the Windows restore workflow is described before the Linux workflow. There are more detailed step-by-step instructions and screenshots for Windows users, while Linux instructions are more concise and lack troubleshooting or advanced usage notes.
Recommendations
  • Add detailed instructions and examples for restoring individual files from SMB snapshots on Linux, including common file operations (cp, rsync) and troubleshooting tips.
  • Include screenshots or terminal output for Linux workflows, similar to the Windows section.
  • Mention Linux file management tools (e.g., rsync, cp) for copying/restoring files from mounted SMB/NFS snapshots.
  • Ensure that Linux workflows are described with equal detail and prominence as Windows workflows.
  • Add a note about mounting SMB shares on macOS and any limitations or differences.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation generally covers both Windows and Linux scenarios for Azure Files, but there is a subtle Windows bias. Windows terminology, features, and examples (such as AD DS, SMB, and PowerShell) are mentioned first or more prominently. Linux support is acknowledged, but Linux-specific instructions, tools, and examples are less detailed or referenced later. Some features (like Azure File Sync and SMB over QUIC) are Windows-only, but the overall guidance could better highlight Linux parity and provide more direct Linux examples.
Recommendations
  • Include explicit Linux mounting examples and CLI commands (e.g., mount -t cifs, mount -t nfs) alongside Windows/PowerShell instructions.
  • When listing supported OSes or protocols, present Linux and Windows equally (not always Windows first).
  • Add references to Linux tools (e.g., smbclient, nfs-utils) and troubleshooting steps for Linux.
  • Where features are Windows-only (e.g., Azure File Sync), clarify alternatives or limitations for Linux users.
  • Ensure links to Linux-specific documentation are as prominent as Windows links.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides step-by-step instructions for managing zonal placement of Azure File Shares via the Azure portal and Azure PowerShell only. There are no examples or guidance for using Azure CLI, which is cross-platform and preferred by many Linux/macOS users. All command-line examples use PowerShell syntax and cmdlets, which are Windows-centric and may create friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, including creating, pinning, and unpinning zonal storage accounts.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant CLI documentation.
  • Consider listing Azure CLI instructions before or alongside PowerShell to promote cross-platform parity.
  • Clarify any limitations if certain features are not available via Azure CLI.
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-14 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 examples for configuring Azure Queue Storage role assignment conditions using the Azure portal and Azure PowerShell, but does not offer equivalent command-line examples for Linux/macOS users (e.g., Azure CLI, Bash). All scripting examples use PowerShell syntax, which is native to Windows and less common on Linux/macOS. This creates friction for non-Windows users who may prefer or require cross-platform tools.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell scripts shown, ensuring Linux/macOS users have clear, native instructions.
  • Explicitly mention that PowerShell Core is available cross-platform, but clarify any differences or requirements for Linux/macOS users.
  • Where possible, provide Bash script snippets or guidance for using REST APIs directly, to further improve parity.
  • In sections where only PowerShell is shown, add a note or link to cross-platform alternatives.
GitHub Create Pull Request
Storage Introduction to Azure Queue Storage ...articles/storage/queues/storage-queues-introduction.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page is generally platform-neutral in its main content, but the 'Next steps' section links to quickstarts that default to Windows-centric tabs (e.g., 'environment-variable-windows') and does not mention Linux/macOS equivalents or provide parity in example visibility. This may subtly signal a preference for Windows environments and create friction for Linux/macOS users seeking platform-specific guidance.
Recommendations
  • Ensure that quickstart links and tabs include Linux/macOS environment variable setup instructions and make them equally visible.
  • Where platform-specific instructions are necessary, provide both Windows and Linux/macOS examples side by side or in clearly labeled tabs.
  • Review linked quickstart pages to confirm that Linux/macOS users are not required to infer steps from Windows instructions.
  • Consider adding a short note in the 'Next steps' section clarifying that Azure Queue Storage is cross-platform and linking to platform-specific setup guides.
GitHub Create Pull Request
Storage Migrate data to Azure with Atempo Miria ...d-partners/data-management/atempo-quick-start-guide.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a detailed walkthrough for migrating data to Azure using Atempo Miria, but the only example for source storage is a Windows file server using SMB/CIFS. There are no examples or guidance for Linux-based sources (such as NFS shares), nor are Linux Data Movers or non-Windows protocols mentioned. Windows terminology and components (e.g., 'Windows Data Mover', 'Windows (CIFS)') are used exclusively in the source configuration section, and the example screenshots and steps are all Windows-centric.
Recommendations
  • Add examples and step-by-step instructions for migrating from Linux-based file servers, such as NFS shares.
  • Include guidance for configuring Linux Data Movers in Miria, and clarify platform support in relevant sections.
  • Present both Windows and Linux source storage options in parallel, or clarify that the example is one of several possible configurations.
  • Reference the Miria compatibility guide directly in the source storage section to highlight supported platforms and protocols.
GitHub Create Pull Request
Storage Considerations for running ISV file services in Azure ...artners/primary-secondary-storage/isv-file-services.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides a broad overview of ISV file services in Azure, but there is a notable bias toward Windows environments. Several ISV solutions (Tiger Technology, XenData) are described as operating specifically on Windows Server, and features like Windows Shell integration and Windows clustering are highlighted. Example use cases and feature tables often mention Windows-centric scenarios (e.g., VDI, Windows file servers) without equivalent Linux/macOS examples or explicit parity. Linux-specific management, deployment, or integration patterns are not discussed, and Linux tools or environments are rarely mentioned except in protocol support (NFS).
Recommendations
  • For each ISV solution, clarify whether Linux/macOS deployments are supported and provide example use cases for those platforms.
  • Where Windows-specific features (e.g., Windows Shell integration, Windows clustering) are mentioned, add notes about Linux/macOS alternatives or limitations.
  • Include Linux/macOS management and deployment examples, such as integration with Linux file servers, Linux-based clustering, or POSIX tools.
  • Expand feature tables to indicate OS support (Windows, Linux, macOS) for each ISV solution.
  • Add guidance for Linux/macOS users on how to achieve parity for features that are Windows-only.
GitHub Create Pull Request
Storage Analyze and migrate your file data to Azure with Data Dynamics StorageX ...partners/data-management/storagex-quick-start-guide.md
Medium Priority View Details →
Scanned: 2026-01-14 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 for Data Dynamics StorageX migration to Azure demonstrates a notable Windows bias. The deployment and installation steps are written with the assumption of a Windows Server environment, including references to Active Directory, Windows file paths (C:\ProgramData\...), and instructions to 'Run as administrator' on the desktop. The only network port checking tool mentioned is Microsoft's portqryui, which is Windows-only. There are no Linux/macOS-specific installation instructions, nor examples for deploying StorageX on non-Windows platforms, even though StorageX supports NFS migrations (common in Linux environments). The documentation does not provide parity for Linux users in terms of installation, service account creation, or troubleshooting.
Recommendations
  • Add explicit instructions or references for deploying StorageX on Linux servers, if supported.
  • Include Linux/macOS equivalents for network port checking (e.g., using netcat, nmap, or telnet).
  • Provide examples for service account creation and privilege assignment on Linux/NFS environments.
  • Clarify whether StorageX server must be Windows-based, or if Linux deployments are supported, and document accordingly.
  • If StorageX is Windows-only, state this clearly at the beginning to set expectations for Linux/macOS users.
GitHub Create Pull Request
Storage Authorize access to blobs using Microsoft Entra ID ...orage/blobs/authorize-access-azure-active-directory.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references PowerShell and the Azure portal (both Windows-centric tools) before mentioning Azure CLI. There are no explicit Linux/macOS examples or mentions of Linux-specific tools or workflows. The phrase 'portal, PowerShell, or Azure CLI' is used, with PowerShell consistently listed before CLI, and no Bash or Linux shell examples are provided. This may create friction for Linux/macOS users who rely on CLI or SDKs in their environments.
Recommendations
  • Add explicit examples for Linux/macOS environments, such as Bash scripts using Azure CLI.
  • When listing tools, alternate the order or mention Azure CLI first to avoid implicit prioritization of Windows tools.
  • Include screenshots or walkthroughs for Azure CLI usage on Linux/macOS.
  • Clarify that all SDKs and CLI commands work cross-platform, and provide links to Linux/macOS installation guides.
  • Avoid grouping PowerShell and CLI together as if they are equivalent; highlight CLI as the preferred cross-platform tool.
GitHub Create Pull Request
Storage Connect to Azure Blob Storage from an SFTP client ...blobs/secure-file-transfer-protocol-support-connect.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides only a Windows PowerShell example for connecting to Azure Blob Storage via SFTP, referencing the Windows OpenSSH implementation. No Linux or macOS-specific examples or instructions are given, and the Windows example is presented first and exclusively. This may create friction for Linux/macOS users who are likely to use native SSH/SFTP clients or command-line shells.
Recommendations
  • Add explicit Linux/macOS examples using the standard 'sftp' command in bash/zsh (e.g., sftp contoso4.contosouser@contoso4.blob.core.windows.net).
  • Clarify that the instructions are cross-platform and that any SFTP client (including those on Linux/macOS) can be used.
  • Provide guidance for installing OpenSSH/SFTP clients on Linux and macOS, or link to relevant documentation.
  • Avoid referencing Windows-specific tools or shells (like PowerShell) exclusively; present examples for multiple platforms side-by-side.
GitHub Create Pull Request
Storage Upgrade Azure Blob Storage with Azure Data Lake Storage capabilities ...rage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md
Medium Priority View Details →
Scanned: 2026-01-13 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 demonstrates a moderate Windows bias. PowerShell instructions are presented prominently and assume a Windows environment ("Open a Windows PowerShell command window"), with no mention of Linux/macOS alternatives for scripting. The Azure CLI section references opening a console such as Windows PowerShell before mentioning Cloud Shell, and does not clarify Linux/macOS terminal usage. There are no Bash or Linux/macOS-specific examples, and Windows tools/patterns are referenced first or exclusively in several places.
Recommendations
  • Clarify that Azure CLI commands can be run from Bash, Linux, and macOS terminals, not just Windows PowerShell.
  • Provide explicit instructions and examples for running PowerShell commands on Linux/macOS using PowerShell Core, or note any limitations.
  • Include Bash shell examples for common tasks, especially for validation and migration steps.
  • Reorder examples so that cross-platform tools (Azure CLI, Portal) are presented before Windows-specific tools (PowerShell).
  • Avoid language that assumes a Windows environment (e.g., 'Open a Windows PowerShell command window'); use 'Open a terminal' or specify platform options.
GitHub Create Pull Request
Storage Use AzCopy v10 in scripts and scheduled transfers ...rticles/storage/common/storage-use-azcopy-in-script.md
Medium Priority View Details →
Scanned: 2026-01-13 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 provides both Linux and Windows examples for scheduling AzCopy tasks, but Windows tools (Schtasks, batch files) are described in greater detail, with additional explanation and links. Windows-specific issues (escaping in .cmd files) are covered, while Linux shell scripting quirks are not. The order of presentation sometimes favors Windows, and PowerShell/Windows command line tools are referenced without Linux equivalents. Jenkins integration is mentioned, but only with a Linux-centric command.
Recommendations
  • Provide equal detail for Linux scheduling tools (e.g., explain crontab parameters as thoroughly as Schtasks).
  • Include Linux-specific scripting caveats (e.g., escaping special characters in bash scripts, permissions).
  • Add examples for macOS where relevant, or clarify cross-platform applicability.
  • Ensure Linux examples are presented first or side-by-side with Windows examples.
  • Reference Linux tools (e.g., systemd timers) as alternatives to cron for advanced scheduling.
GitHub Create Pull Request
Storage Migrate to Transport Layer Security (TLS) 1.2 for Azure Blob Storage ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-migrate-to-TLS2.md
Medium Priority View Details →
Scanned: 2026-01-13 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. Quick Tips and guidance primarily reference Windows OS versions, .NET Framework, Visual Studio, and PowerShell, with no explicit mention of Linux/macOS equivalents or examples. Tools like Fiddler and instructions for enabling TLS are Windows-centric. There are no examples or recommendations for Linux/macOS users, such as how to check or enforce TLS 1.2 on those platforms.
Recommendations
  • Add explicit guidance for Linux and macOS users, including how to verify and enforce TLS 1.2 (e.g., using OpenSSL, curl, or system configuration files).
  • Provide examples for popular Linux/macOS development stacks (e.g., Python, Java, Node.js) showing how to ensure TLS 1.2 is used.
  • Mention Linux/macOS default TLS support (e.g., most modern distributions enable TLS 1.2 by default) in the Quick Tips section.
  • List cross-platform tools for TLS inspection (e.g., OpenSSL, curl with verbose output) alongside Fiddler and Qualys SSL Labs.
  • Ensure that links to further instructions include Linux/macOS-specific content or alternatives.
GitHub Create Pull Request
Storage Data Redundancy in Azure Files ...s/blob/main/articles/storage/files/files-redundancy.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates moderate Windows bias. While the core content is platform-neutral, the only explicit example of Azure File Sync for geo-redundancy references 'an on-premises Windows file server' and does not mention Linux alternatives. The scripting examples for region supportability are provided for both PowerShell (Windows-centric) and Azure CLI (cross-platform), but PowerShell is presented first. The only tool mentioned for scripting file copy is AzCopy, which is cross-platform, but the disaster recovery scenario focuses on Windows file servers. There are no Linux-specific examples or references to Linux file servers or NFS-based disaster recovery patterns.
Recommendations
  • Include explicit examples and guidance for Linux/macOS users, such as using NFS file shares for geo-redundancy and disaster recovery.
  • Mention Linux file servers as valid endpoints for Azure File Sync or provide alternative sync/copy strategies for Linux environments.
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first to emphasize cross-platform parity.
  • Provide links or references to Linux-specific documentation for Azure Files and disaster recovery scenarios.
GitHub Create Pull Request
Storage Manage block blobs with Azure CLI ...zure-docs/blob/main/articles/storage/blobs/blob-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides Azure CLI examples exclusively in Bash, which is cross-platform, but consistently uses Windows-style file paths (e.g., C:\temp\) and references to Windows directories. There are no Linux/macOS path examples, and instructions for creating required files (like XML) assume a Windows environment. This may cause confusion or friction for Linux/macOS users, as they must mentally translate paths and file locations. No PowerShell examples are present, and Windows tools are not mentioned exclusively, but the Windows-centric pathing is a subtle but persistent bias.
Recommendations
  • Provide Linux/macOS path examples alongside Windows paths (e.g., /home/user/temp/).
  • Explicitly note that Bash scripts and Azure CLI work on all platforms, and clarify any platform-specific differences.
  • For file creation instructions, offer both Windows and Linux/macOS approaches.
  • Where sample code references file paths, use environment variables or platform-agnostic placeholders.
  • Add a note early in the documentation about path conventions and how to adapt examples for non-Windows systems.
GitHub Create Pull Request
Storage Access control lists in Azure Data Lake Storage ...cles/storage/blobs/data-lake-storage-access-control.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page lists Windows-centric tools (Azure Storage Explorer, PowerShell) before cross-platform or Linux-native options, and provides explicit PowerShell and Azure CLI examples for identity management. The guidance for managing ACLs references Windows tools and patterns first, with Linux-specific methods (such as setfacl or POSIX CLI tools) absent or only mentioned in external links. The primary workflow examples and instructions are oriented toward Windows environments, potentially creating friction for Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS command-line examples for managing ACLs, such as using Azure CLI or REST API from Bash.
  • Include references and examples for POSIX ACL management tools (e.g., setfacl, getfacl) where relevant.
  • Balance the order of tool recommendations, listing cross-platform options (Azure CLI, REST API) before Windows-specific tools.
  • Provide guidance for managing ACLs from Linux environments, including authentication and scripting patterns.
  • Clarify that Azure Storage Explorer is available on Linux/macOS and provide installation instructions for those platforms.
GitHub Create Pull Request
Storage Filter data by using Azure Data Lake Storage query acceleration ...e/blobs/data-lake-storage-query-acceleration-how-to.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides PowerShell examples and instructions for installing the Az PowerShell module, which is primarily a Windows-centric tool. PowerShell is presented as the only command-line example, with no equivalent Bash, CLI, or Linux shell examples. The instructions for .NET, Java, Python, and Node.js are cross-platform, but the only OS-specific tooling mentioned is PowerShell. There is no mention of Linux/macOS command-line alternatives, and PowerShell is listed first in most code example sections.
Recommendations
  • Add Azure CLI examples for each scenario, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples for common tasks, such as installing SDKs or querying blobs.
  • Clarify that PowerShell examples can be run on Linux/macOS using PowerShell Core, or provide explicit instructions for those platforms.
  • Reorder examples so that cross-platform tools (e.g., Azure CLI) are presented before Windows-specific tools.
  • Explicitly mention Linux/macOS compatibility in prerequisites and setup sections.
GitHub Create Pull Request
← Previous Page 43 of 67 Next →