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 576-600 of 1657 flagged pages
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-extension.md ...main/articles/storage/file-sync/file-sync-extension.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is exclusively focused on Windows servers, both in prerequisites and all examples. It explicitly states that Azure File Sync is only supported on Windows, and all instructions, settings, and validation steps reference Windows-specific tools, paths, and concepts (e.g., C:\Program Files, Programs and Features, FileSyncSvc). There are no Linux equivalents, examples, or even mention of Linux support or alternatives. Windows terminology and tools (PowerShell, Windows file paths, Windows services) are used throughout, and Linux is only mentioned to clarify lack of support.
Recommendations
  • Clearly state Windows-only support in the introduction and prerequisites, and link to alternative solutions for Linux file sync if available.
  • If Azure File Sync support for Linux is planned, add a roadmap or note for parity.
  • Provide guidance or references for Linux users seeking similar functionality (e.g., Azure File Share mounting on Linux, third-party sync tools).
  • Where possible, use cross-platform Azure CLI examples and clarify which commands/settings are Windows-specific.
  • Add a comparison table or FAQ section explaining why Linux is not supported and what alternatives exist.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples for metric analysis, referencing PowerShell before Azure CLI, and omitting explicit Linux/bash shell examples. While Azure CLI is included (which is cross-platform), there are no bash or Linux-native command examples, and the troubleshooting link references a Windows-specific tab. The .NET SDK section is platform-neutral, but the overall pattern prioritizes Windows/PowerShell workflows.
Recommendations
  • Add bash/Linux shell examples alongside PowerShell, especially for common metric queries using Azure CLI.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide sample terminal output or shell scripts.
  • Ensure troubleshooting and related links include Linux-specific tabs or guidance, not just Windows.
  • Balance the order of examples so that Azure CLI or cross-platform options are presented before or alongside PowerShell.
  • Where screenshots or instructions reference the Azure portal, clarify that the experience is the same across OSes.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-planning.md .../main/articles/storage/file-sync/file-sync-planning.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. Azure File Sync is described as a solution specifically for Windows Server, with all deployment, management, and troubleshooting examples and tools (such as PowerShell cmdlets and NTFS-specific features) focused exclusively on Windows environments. There are no Linux equivalents or examples, and Windows terminology and tools are presented first and exclusively throughout the document.
Recommendations
  • Clearly state in the introduction that Azure File Sync is a Windows Server-only solution and provide guidance for Linux users on alternative approaches (e.g., mounting Azure Files directly via SMB/NFS).
  • Where possible, offer parity by referencing Linux/macOS options for file share access, backup, and migration, even if Azure File Sync itself is not supported.
  • Add a comparison table or section outlining differences between Windows and Linux support for Azure Files, including sync, backup, and security features.
  • Provide links to Linux-focused documentation for Azure Files (e.g., mounting, authentication, backup) in the 'Related content' section.
  • If future support for non-Windows platforms is planned, note this and provide a roadmap or alternatives.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-replace-server.md ...articles/storage/file-sync/file-sync-replace-server.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively references Windows Server as the platform for Azure File Sync, with all steps and tooling (e.g., Robocopy, DFS-N) being Windows-specific. There are no Linux equivalents, examples, or mentions, and the workflow assumes a Windows environment throughout.
Recommendations
  • Clarify in the introduction that Azure File Sync is currently only supported on Windows Server, if that is the case. If Linux support is planned or available, provide equivalent instructions and tooling for Linux environments.
  • Where possible, mention cross-platform alternatives to Windows-only tools (e.g., suggest rsync as an alternative to Robocopy for Linux).
  • If DFS-N is not available on Linux, suggest alternative methods for user cut-over on Linux systems (such as symbolic links, NFS exports, or Samba configurations).
  • Explicitly state platform limitations and provide guidance for mixed or non-Windows environments, or link to relevant documentation for Linux users.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/create-file-share.md .../blob/main/articles/storage/files/create-file-share.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as a primary automation example, and the term 'PowerShell' is explicitly called out before Azure CLI. The CLI example is generic and not specifically tailored for Linux, and there are no bash or Linux shell script examples. The portal instructions and screenshots are Windows-centric (Azure portal is most commonly accessed from Windows environments), and there is no mention of Linux-specific tooling or patterns in the main workflow. The 'Next steps' section does link to Linux-specific guides, but the main content prioritizes Windows tools and patterns.
Recommendations
  • Add explicit Linux shell/bash examples for resource creation, possibly using curl or REST API calls.
  • Clarify that Azure CLI commands can be run natively on Linux and provide Linux-specific usage notes (e.g., installation, authentication).
  • Include screenshots or instructions for accessing the Azure portal from Linux environments (e.g., via Firefox on Ubuntu).
  • Mention Linux-native automation tools (e.g., Ansible, Terraform) for file share provisioning.
  • Ensure parity in examples by presenting Azure CLI before PowerShell, or side-by-side, to avoid Windows-first ordering.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-extend-servers.md ...articles/storage/file-sync/file-sync-extend-servers.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server and Windows-based tools. All examples, instructions, and screenshots are for Windows Server 2019 Datacenter VMs, with no mention of Linux or cross-platform alternatives. The use of Windows-specific tools such as PowerShell, Internet Explorer, and Windows Server Manager is pervasive, and there are no Linux equivalents or parity guidance provided.
Recommendations
  • Add a section clarifying platform support, explicitly stating whether Azure File Sync is Windows-only or if Linux support is available/planned.
  • If Linux support exists, provide parallel instructions and examples for deploying Azure File Sync on Linux servers, including relevant tools and commands.
  • Where possible, offer cross-platform alternatives to Windows-specific tools (e.g., use Azure CLI instead of PowerShell, or provide both).
  • Include a comparison table of supported operating systems and features to help users understand platform limitations.
  • If Azure File Sync is Windows-only, make this clear early in the documentation to set expectations and direct Linux users to alternative solutions.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-introduction.md ...n/articles/storage/file-sync/file-sync-introduction.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Azure File Sync exhibits a strong Windows bias. All examples, deployment scenarios, and operational instructions reference Windows Server exclusively, with no mention of Linux or cross-platform alternatives. The service is described as transforming Windows Server into a cache, and all recovery, migration, and backup workflows assume Windows environments. There are no Linux examples, nor is there discussion of using Azure File Sync with Linux servers or tools.
Recommendations
  • Add explicit statements about platform support, clarifying whether Linux servers can participate in Azure File Sync, and if not, explain the limitations.
  • If Linux support is possible, provide equivalent Linux examples, workflows, and tooling instructions (e.g., using SMB/NFS on Linux, agent installation, recovery steps).
  • Mention Linux file server scenarios in migration and backup sections, including how to transition from Linux-based file shares to Azure Files.
  • Include cross-platform comparison tables or guidance for organizations with mixed Windows/Linux environments.
  • If Azure File Sync is Windows-only, recommend alternative solutions for Linux users and link to relevant documentation.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-change-redundancy-configuration.md ...storage/files/files-change-redundancy-configuration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently listing PowerShell as a primary method for command-line operations, often before Azure CLI, and by providing only PowerShell and Azure CLI examples for scripting. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or workflows. The use of PowerShell as a default scripting language and the absence of Linux shell examples may disadvantage Linux users or those unfamiliar with PowerShell.
Recommendations
  • Add bash shell examples alongside PowerShell and Azure CLI, especially for common operations (e.g., using az commands in bash scripts).
  • Explicitly mention Linux compatibility for Azure CLI commands and provide sample usage in a Linux terminal context.
  • Include notes or sections clarifying that all CLI commands are cross-platform and provide guidance for Linux users where workflows may differ.
  • Avoid listing PowerShell before Azure CLI in all cases; alternate or group them together to avoid implying a Windows-first approach.
  • Reference Linux-native tools (e.g., AzCopy usage in Linux, scripting with sh/bash) where manual migration or automation is discussed.
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: 2026-01-08 00:53
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 exclusively referencing Windows ACLs for access control, mentioning Windows tools (robocopy) for data migration, and omitting Linux equivalents or examples. The terminology and examples are centered around Windows environments, with no guidance for Linux users on managing ACLs or migrating data.
Recommendations
  • Include examples and guidance for managing ACLs on Azure Files from Linux clients, such as using setfacl, getfacl, or relevant SMB client tools.
  • Mention Linux-compatible tools for migrating files and preserving ACLs, such as rsync (with SMB support), smbclient, or cifs-utils.
  • Clarify whether and how POSIX ACLs are supported or mapped in Azure Files, and provide documentation links or examples for Linux users.
  • Balance references to Windows and Linux environments throughout the documentation, ensuring parity in instructions and tool recommendations.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
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 equivalents or cross-platform alternatives. All code samples are in PowerShell, and prerequisites explicitly require Windows environments. There is no guidance for administrators working from Linux or macOS systems.
Recommendations
  • Provide equivalent instructions for Linux environments, such as using LDAP tools (e.g., ldapmodify, ldappasswd) or cross-platform scripting languages (Python with ldap3).
  • Clarify whether password rotation and Kerberos key management can be performed from non-Windows clients, and document any limitations.
  • Include examples using Azure CLI or REST API if available, as these are cross-platform.
  • Explicitly state platform requirements and, if Windows is required, explain why and suggest alternatives or workarounds for Linux/macOS users.
  • Add a section comparing Windows and Linux approaches, highlighting any differences in procedure or tooling.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-server-hybrid-databox.md ...files/storage-files-migration-server-hybrid-databox.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows Server as the source environment for Azure File Sync migrations with Azure Data Box. All examples, instructions, and migration paths assume the use of Windows Server (2012 R2 or newer) and Windows-native tools (Robocopy). There is no mention of Linux servers, Linux file systems, or Linux-compatible migration tools. The documentation does not provide parity for Linux environments, nor does it offer alternative guidance for non-Windows scenarios within this guide.
Recommendations
  • Add explicit statements clarifying the scope of the guide (e.g., 'This guide is for Windows Server environments only').
  • Provide links to equivalent Linux migration guides or create a parallel guide for Linux/NAS environments using Azure Data Box.
  • Include examples or references for Linux-compatible file copy tools (such as rsync, cp, or Azure CLI) where applicable.
  • Mention limitations or unsupported scenarios for Linux servers in the introduction and migration overview.
  • Ensure that migration overview and scenario selection sections clearly direct Linux/NAS users to appropriate resources.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-smb-protocol.md ...blob/main/articles/storage/files/files-smb-protocol.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias in several ways: Windows terminology and tools (e.g., PowerShell, registry keys, Set-SmbClientConfiguration) are used exclusively or explained in detail, especially for advanced SMB features and security settings. All client-side configuration examples for enabling encryption ciphers or SMB Multichannel fixes are for Windows, with no Linux (or macOS) equivalents provided. Windows-based application scenarios are highlighted before others, and Windows-specific limitations and references are frequent. Linux is only mentioned in passing, with no concrete examples or parity in advanced configuration guidance.
Recommendations
  • Provide equivalent Linux (and macOS) client configuration examples for SMB Multichannel, encryption ciphers, and other advanced SMB features, using tools like smb.conf, mount.cifs, or relevant commands.
  • When discussing client-side requirements or fixes (e.g., enabling SMB Multichannel, setting encryption ciphers), include both Windows and Linux/macOS instructions, or explicitly state if a feature is not supported on non-Windows platforms.
  • Balance scenario descriptions by including Linux-based application use cases and not focusing primarily on Windows-based workloads.
  • Reference Linux and macOS documentation and tools (e.g., Samba, cifs-utils) alongside Windows tools when discussing SMB protocol support, security, and compatibility.
  • Where PowerShell is used for Azure management, ensure that Azure CLI and REST API examples are equally detailed and not just a translation of PowerShell scripts.
  • Explicitly mention any feature gaps or differences for Linux/macOS clients, and provide troubleshooting or workaround guidance where possible.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-planning.md .../main/articles/storage/files/storage-files-planning.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias in several ways: Windows terminology and tools (such as Azure File Sync, Active Directory Domain Services, and PowerShell) are mentioned first or exclusively in key sections. The caching solution (Azure File Sync) is only available for Windows Server, and Windows-centric authentication and networking patterns are emphasized. While Linux is mentioned (especially for NFS and SMB support), examples, recommendations, and tooling references are predominantly Windows-focused, with limited or no equivalent Linux guidance or examples provided.
Recommendations
  • Provide Linux-specific examples and guidance for mounting SMB and NFS shares, including recommended tools and commands (e.g., mount.cifs, mount.nfs, smbclient).
  • Highlight Linux-compatible caching or synchronization solutions, or clarify the lack thereof and suggest alternatives for Linux environments.
  • Ensure parity in authentication documentation by including detailed steps for configuring identity-based authentication for Linux clients, not just referencing AD DS.
  • Include CLI and scripting examples using Bash or Linux-native tools alongside PowerShell examples.
  • Order OS mentions in tables and lists alphabetically or by protocol relevance, rather than defaulting to Windows first.
  • Explicitly state limitations or differences for Linux environments where features (such as Azure File Sync) are Windows-only, and suggest workarounds or alternatives.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-configure-file-level-permissions.md ...torage-files-identity-configure-file-level-permissions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 strong Windows bias. All examples and instructions for configuring directory and file-level permissions are exclusively based on Windows tools and workflows (e.g., icacls, Windows File Explorer, PowerShell). The page assumes the use of Windows ACLs (NTFS permissions) and provides no Linux-specific guidance or examples for managing permissions on Azure file shares. Windows terminology and tools are mentioned first and exclusively, with no parity for Linux users, despite Azure Files supporting SMB mounts on Linux.
Recommendations
  • Add Linux-specific instructions and examples for mounting Azure file shares and managing permissions, such as using 'mount.cifs' and 'setfacl' or 'chmod' where possible.
  • Clarify whether and how Linux clients can interact with Windows ACLs on Azure Files, including any limitations or differences in enforcement.
  • Provide parity in documentation structure: introduce Linux tools and workflows alongside Windows ones, not only after or as an afterthought.
  • Include troubleshooting tips for Linux users, such as dealing with permission mapping between POSIX and Windows ACLs.
  • Explicitly state any features or limitations for Linux clients regarding ACL management, so Linux administrators can plan accordingly.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-performance-checklist.md ...ticles/storage/queues/storage-performance-checklist.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates mild Windows bias. It mentions Windows-specific tools (Network Monitor), references PowerShell and Azure CLI together but does not provide Linux-specific examples or mention Linux tools (e.g., tcpdump) for network diagnostics. The .NET configuration section is Windows/.NET-centric, with no equivalent guidance for Linux or other platforms. Windows tools are mentioned before any Linux alternatives, and examples are only given for .NET/Windows environments.
Recommendations
  • Add Linux-specific tools for network diagnostics, such as tcpdump or iftop, alongside Wireshark.
  • Provide configuration examples for popular Linux environments and languages (e.g., Python, Java) for connection/thread pool management.
  • Explicitly mention cross-platform compatibility for Azure CLI and PowerShell, and provide usage examples for both Windows and Linux shells.
  • Include links or references to Linux/macOS documentation where relevant.
  • Balance .NET-specific advice with equivalent recommendations for other major platforms (Java, Python, Node.js).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-storage-monitoring-scenarios.md ...les/storage/blobs/blob-storage-monitoring-scenarios.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias. PowerShell is used as the primary example for decoding SAS tokens, and Windows-centric tools (PowerShell, Azure portal) are referenced before Linux alternatives. Although a Linux command-line example is provided for hashing SAS tokens, it appears after the PowerShell example. There is no mention of Linux-native tools (e.g., bash, openssl) for other tasks, and the workflow assumes familiarity with Windows/Azure portal navigation.
Recommendations
  • Provide Linux/bash equivalents for all PowerShell examples, and present them alongside or before Windows examples.
  • Reference cross-platform tools (e.g., Azure CLI, REST API) for tasks such as viewing logs or decoding tokens.
  • Include screenshots or instructions for Linux environments where applicable (e.g., Azure CLI usage in terminal).
  • Clarify that all examples can be executed on both Windows and Linux, and highlight any platform-specific differences.
  • Avoid assuming the Azure portal is the primary interface; mention alternatives like Azure CLI or SDKs.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/authorize-access-azure-active-directory.md ...orage/blobs/authorize-access-azure-active-directory.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
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 before Azure CLI, grouping them together, and not providing explicit Linux or cross-platform command examples. The references to PowerShell are frequent, and there is no mention of Linux-specific tools, shell environments, or usage patterns. The documentation does not provide parity in examples or guidance for Linux users, nor does it clarify cross-platform differences in authentication or tooling.
Recommendations
  • Explicitly provide Linux shell (bash) examples alongside PowerShell, especially for authentication and data access tasks.
  • When referencing command-line tools, mention Azure CLI first or equally with PowerShell, and clarify that Azure CLI is cross-platform.
  • Include notes or sections on using these tools in Linux/macOS environments, such as installing Azure CLI on Linux, using bash scripts, or authenticating with Microsoft Entra ID from Linux.
  • Avoid grouping PowerShell and Azure CLI together without clarifying their platform support; highlight Azure CLI as the recommended cross-platform tool.
  • Add troubleshooting or environment-specific guidance for Linux users, such as handling token credentials or environment variables in bash.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/archive-rehydrate-handle-event.md ...ticles/storage/blobs/archive-rehydrate-handle-event.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a clear Windows bias by exclusively using Visual Studio (a Windows-centric IDE) for all development and deployment steps, specifying Windows as the required operating system for the Function App, and omitting any guidance or examples for Linux or cross-platform development environments. No mention is made of alternatives such as Visual Studio Code, Azure CLI, or command-line tooling that would enable Linux or macOS users to follow the tutorial. All screenshots and instructions are tailored to Windows users, and there is no parity in instructions or tooling for Linux environments.
Recommendations
  • Add parallel instructions and examples for developing and deploying Azure Functions using Visual Studio Code, Azure CLI, or other cross-platform tools.
  • Explicitly mention that Azure Functions can be developed and deployed from Linux and macOS, and provide links to relevant documentation.
  • Include instructions for creating a Function App with the operating system set to Linux, and clarify any differences in the process.
  • Provide code snippets and package installation commands using dotnet CLI (cross-platform) in addition to Visual Studio and PowerShell examples.
  • Ensure screenshots and UI instructions are not exclusively from Windows environments, or provide alternative visuals for Linux/macOS users.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-acl-azure-portal.md ...es/storage/blobs/data-lake-storage-acl-azure-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 primarily referencing Windows-centric tools (Azure Storage Explorer, PowerShell) and mentioning them before cross-platform or Linux-native equivalents. There are no explicit Linux or bash examples, nor is there mention of Linux-specific tools or command-line patterns. The Azure CLI is referenced, but only after Windows tools, and without any example or parity guidance for Linux users.
Recommendations
  • Provide explicit Linux/bash examples for managing ACLs, especially for recursive operations.
  • Mention Azure CLI as a cross-platform tool before or alongside Windows tools like PowerShell and Storage Explorer.
  • Include screenshots or instructions for Linux environments where applicable.
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide sample commands for both shells.
  • Reference Linux-native tools or patterns if relevant, or note their absence if Azure-specific tooling is required.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-query-acceleration-how-to.md ...e/blobs/data-lake-storage-query-acceleration-how-to.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page displays a Windows bias by providing PowerShell examples and instructions for installing the Az PowerShell module, which is primarily a Windows tool. PowerShell is presented as a first-class tab alongside cross-platform SDKs, but there are no equivalent Linux shell (bash, zsh) or CLI examples. The instructions for .NET reference 'command prompt', which is a Windows-centric term, and there is no mention of Linux-specific tools or patterns. No Linux shell or Azure CLI examples are given, and PowerShell is listed before other SDKs in most sections.
Recommendations
  • Add Azure CLI examples for each scenario, as Azure CLI is cross-platform and widely used on Linux.
  • Provide bash/zsh shell script examples for installation and usage, especially for Linux users.
  • Clarify that PowerShell Core is available cross-platform, but provide explicit bash/CLI alternatives.
  • Replace or supplement 'command prompt' instructions with 'terminal' and include Linux/Mac equivalents.
  • Ensure that Linux tools and patterns (e.g., curl, jq, Azure CLI) are mentioned and demonstrated alongside or before Windows-specific tools.
  • Consider reordering tabs so that cross-platform tools (CLI, SDKs) appear before Windows-specific tools like PowerShell.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/object-replication-configure.md ...articles/storage/blobs/object-replication-configure.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides extensive PowerShell examples and references, which are primarily associated with Windows environments. PowerShell is presented as a first-class method alongside Azure CLI and portal, but its usage and file path conventions (e.g., C:\temp\json.txt) reinforce a Windows-centric approach. There are no Linux shell (bash) or cross-platform scripting examples, and file system references are Windows-specific. The documentation does not mention or provide parity for Linux-native tools, nor does it address platform differences in scripting or file handling.
Recommendations
  • Add bash shell examples for all CLI operations, including scripting and file handling, to demonstrate Linux parity.
  • Use platform-neutral file path conventions (e.g., /tmp/json.txt) or provide both Windows and Linux file path examples.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide guidance for installation and usage on non-Windows platforms.
  • Where PowerShell is referenced, clarify that PowerShell Core is available cross-platform, and provide examples for Linux/macOS where file paths or behaviors differ.
  • Avoid assuming a Windows environment in examples and instructions; where necessary, provide notes or alternatives for Linux users.
  • Consider including references to Linux-native tools (e.g., curl for REST API calls) where appropriate.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-access-control.md ...cles/storage/blobs/data-lake-storage-access-control.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. In the 'How to set ACLs' section, Windows-centric tools (Azure Storage Explorer, Azure portal, PowerShell) are listed before cross-platform or Linux-native tools (Azure CLI, REST API). PowerShell is given its own example, and Storage Explorer is highlighted as a primary management tool, both of which are more commonly used on Windows. There is no mention of Linux shell commands (e.g., setfacl, getfacl) or native POSIX ACL management tools, nor are there examples using Linux command-line utilities. The documentation assumes Azure CLI as the main cross-platform command-line tool, but does not provide parity with Linux-specific workflows or examples.
Recommendations
  • Add explicit Linux/POSIX command-line examples for managing ACLs, such as using setfacl/getfacl on mounted Data Lake Storage via NFS or similar interfaces.
  • Include references to Linux-native tools and workflows for ACL management, especially for users working in Linux environments or with Hadoop/HDFS.
  • Reorder the 'How to set ACLs' table to present cross-platform tools (Azure CLI, REST API) before Windows-centric tools (PowerShell, Storage Explorer).
  • Provide guidance or links for Linux users on integrating Azure Data Lake Storage with Linux file systems and managing ACLs using familiar Linux commands.
  • Clarify which tools are cross-platform and which are Windows-specific, helping users choose the best tool for their environment.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-best-practices.md ...cles/storage/blobs/data-lake-storage-best-practices.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by frequently listing Windows-centric tools (PowerShell, Azure portal) before cross-platform or Linux-native equivalents (Azure CLI, REST, DistCp). PowerShell is repeatedly referenced for ingestion, management, and monitoring tasks, often before or alongside Azure CLI, but with no explicit Linux shell or scripting examples. There is a lack of Linux-specific guidance or examples (e.g., Bash, shell scripts, Linux desktop tools), and Windows/PowerShell tools are presented as default or primary options. No explicit Linux command-line or workflow examples are provided, and Windows VM types are recommended for hardware optimization without mention of Linux VM types.
Recommendations
  • Provide Linux/Bash shell examples alongside PowerShell for all command-line operations.
  • Explicitly mention Linux VM types and optimization strategies when discussing hardware recommendations.
  • List cross-platform tools (Azure CLI, REST, AzCopy, DistCp) before Windows-centric tools (PowerShell, Azure portal) in tables and guidance.
  • Include references to Linux desktop tools (e.g., GNOME/KDE file managers, Linux Storage Explorer usage) where appropriate.
  • Add guidance for Linux-based automation and scripting (e.g., Bash scripts for ingestion, monitoring, and management).
  • Ensure parity in troubleshooting and monitoring instructions for Linux environments (e.g., systemd, Linux logging tools).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/network-file-system-protocol-known-issues.md ...age/blobs/network-file-system-protocol-known-issues.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by mentioning Windows client support status before Linux, referencing PowerShell as a method for enabling static websites, and lacking explicit Linux command examples for NFS mounting and management. While it does mention a workaround for Windows (WSL 2), it does not provide concrete Linux usage examples or parity in tooling references.
Recommendations
  • Add explicit Linux command-line examples for mounting NFS shares (e.g., using mount -t nfs).
  • Reference common Linux tools (such as nfs-utils, showmount, exportfs) alongside or before Windows/PowerShell equivalents.
  • Provide Azure CLI examples for static website configuration, not just PowerShell.
  • Clarify Linux client compatibility and provide troubleshooting steps for common Linux distributions.
  • Ensure that Linux patterns and tools are mentioned at least as prominently as Windows/PowerShell options.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/monitor-blob-storage.md ...ob/main/articles/storage/blobs/monitor-blob-storage.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for monitoring Azure Blob Storage, with PowerShell presented before Azure CLI. While Azure CLI is cross-platform, the prominence and depth of PowerShell coverage (a Windows-centric tool) and the lack of explicit Linux shell or scripting examples (e.g., Bash) indicate a Windows-first and PowerShell-heavy bias. There are no Linux-specific instructions or examples, and no mention of Linux-native tools or patterns.
Recommendations
  • Provide Bash shell examples alongside PowerShell, especially for Azure CLI commands, to demonstrate parity and usability on Linux systems.
  • Reorder or parallelize example sections so that Azure CLI (cross-platform) appears before or alongside PowerShell, rather than after.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample command-line environments for each.
  • Include troubleshooting or usage notes relevant to Linux environments (e.g., authentication methods, file paths, environment variables).
  • Where SDKs are shown (e.g., .NET), consider referencing or linking to equivalent SDK usage in Python or Java, which are popular on Linux.
GitHub Create Pull Request
← Previous Page 24 of 67 Next →