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 776-800 of 1657 flagged pages
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/sas-expiration-policy.md .../main/articles/storage/common/sas-expiration-policy.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting PowerShell instructions before Azure CLI, using PowerShell-specific cmdlets, and referencing Windows-centric tooling and patterns. While Azure CLI is included, the PowerShell section is more detailed and appears before the CLI, which is more cross-platform. There are no Linux- or Bash-specific examples, and the documentation does not mention or show screenshots from Linux environments.
Recommendations
  • Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more accessible to Linux users.
  • Include Bash shell examples and clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • Add notes or screenshots showing the process in Linux terminal environments where relevant.
  • Where PowerShell is mentioned, also mention that Azure CLI is available and preferred for Linux/macOS users.
  • Avoid using Windows-specific terminology or screenshots exclusively; include Linux equivalents or clarify cross-platform compatibility.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-release-notes.md .../articles/storage/file-sync/file-sync-release-notes.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for Azure File Sync is heavily biased toward Windows environments. All instructions, requirements, and examples are exclusively for Windows Server, with repeated references to Windows-specific tools (e.g., PowerShell cmdlets, Robocopy, NTFS, FSRM, .NET Framework). There is no mention of Linux support, alternatives, or parity, and no Linux or cross-platform examples are provided. The documentation assumes the reader is operating in a Windows-only context.
Recommendations
  • Clearly state early in the documentation whether Azure File Sync is supported only on Windows Server, and if so, explain why and whether Linux support is planned.
  • If partial Linux support exists (e.g., for Azure Files itself), provide guidance or links for Linux users on how to interact with Azure Files, even if sync agent parity is not available.
  • Where PowerShell cmdlets are referenced, offer equivalent CLI or REST API commands if available, and clarify their platform compatibility.
  • Avoid using only Windows-specific tools (e.g., Robocopy, FSRM) in examples; if alternatives exist for Linux, mention them.
  • Add a section explicitly addressing cross-platform considerations, including limitations and possible workarounds for non-Windows environments.
  • If Azure File Sync is fundamentally a Windows-only solution, make this limitation prominent and suggest alternative architectures for Linux users.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-migrate-on-premises-data.md .../common/storage-use-azcopy-migrate-on-premises-data.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. Windows-specific tools (Schtasks) are mentioned before their Linux equivalents (crontab), and Windows paths/examples are often listed first. There is a tendency to explain Windows concepts and commands in more detail, and some sections (such as authentication and script creation) provide more explicit guidance for Windows users. Linux examples are present but sometimes less detailed or appear after Windows content.
Recommendations
  • Alternate the order in which Windows and Linux examples are presented, or present them side-by-side to avoid always listing Windows first.
  • Ensure that all explanations and command breakdowns are equally detailed for both Windows and Linux users.
  • Where possible, provide parity in example scripts and command-line usage, including full Linux shell script examples (not just commands).
  • Expand on Linux-specific instructions, such as setting environment variables for authentication in cron jobs, and provide troubleshooting tips for both platforms.
  • Use neutral language when introducing cross-platform tools, and avoid implying Windows as the default or primary environment.
  • Include macOS examples where relevant, especially for script creation and scheduling.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation assumes the use of Windows Server exclusively, with all steps, tools, and examples (such as Robocopy and DFS-N) being Windows-specific. There are no Linux equivalents or cross-platform guidance, and the documentation does not acknowledge the possibility of non-Windows environments.
Recommendations
  • Clarify early in the documentation whether Azure File Sync supports only Windows Server, or provide guidance for Linux or cross-platform scenarios if available.
  • If Linux support is possible, include equivalent Linux commands and tools (e.g., rsync instead of Robocopy) for file copying.
  • Mention Linux-compatible alternatives to DFS-N for namespace redirection, or explicitly state if such functionality is unavailable.
  • Structure instructions to acknowledge both Windows and Linux environments, or explain the Windows-only limitation up front.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-redundancy.md ...s/blob/main/articles/storage/files/files-redundancy.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways. PowerShell examples are given in full detail before the Azure CLI/Linux equivalent, and the PowerShell section is more verbose and prominent. Windows-specific tools and scenarios (such as Azure File Sync with Windows file servers) are described in detail, while Linux/NFS scenarios are less emphasized or omitted. There are no Linux/NFS-specific redundancy or failover examples, and the documentation does not provide parity in guidance or troubleshooting for Linux clients.
Recommendations
  • Provide Linux/NFS-specific examples and scenarios, especially for redundancy, failover, and disaster recovery.
  • Ensure that Azure CLI/bash examples are given equal prominence and detail as PowerShell examples, possibly presenting CLI first or side-by-side.
  • Include troubleshooting and operational guidance for Linux/NFS clients, not just SMB/Windows clients.
  • Mention and link to Linux tools (e.g., rsync, cron, Linux mount options) where relevant, especially in sections discussing custom scripts or sync solutions.
  • Clarify any differences in redundancy support or behavior for NFS/Linux clients versus SMB/Windows clients.
  • Balance the documentation so that Windows and Linux users can both find relevant, actionable information for their platforms.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/shared-key-authorization-prevent.md ...les/storage/common/shared-key-authorization-prevent.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is given a dedicated example section before the Azure CLI, and Azure PowerShell is referenced as a primary tool for managing storage accounts. The Azure Storage Explorer documentation link defaults to Windows tabs, and the Azure portal (which is often used on Windows) is emphasized. There are no explicit Linux shell (bash) or cross-platform scripting examples, and no mention of Linux-specific tools or workflows. While Azure CLI is included, it is presented after PowerShell, and there is no explicit parity guidance for Linux users.
Recommendations
  • Provide bash or shell script examples alongside PowerShell, especially for common tasks such as updating storage account properties.
  • Ensure that Azure CLI examples are presented before or alongside PowerShell to emphasize cross-platform compatibility.
  • When referencing Azure Storage Explorer or other tools, include instructions or links for Linux and macOS versions, not just Windows.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
  • Where screenshots or UI walkthroughs are given, clarify if the experience differs on non-Windows platforms.
  • Consider including a table or section summarizing tool availability and usage across different operating systems.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-delete.md ...ain/articles/storage/elastic-san/elastic-san-delete.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting Windows/Powershell instructions and scripts before Linux/CLI equivalents, using Powershell as the primary example for deletion commands, and referencing Windows-specific tools and patterns. Linux instructions are present but are consistently positioned after Windows ones, and the scripting approach for Linux is less integrated (Python script vs. native shell).
Recommendations
  • Alternate the order of Windows and Linux sections, or present them side-by-side to avoid privileging one platform.
  • Provide native Bash/shell script examples for Linux users, not just Python scripts.
  • Ensure that Azure CLI examples are given equal prominence to PowerShell, possibly by combining them in unified tabs or sections.
  • Explicitly state that both Windows and Linux are fully supported and provide parity in instructions and tooling.
  • Review terminology to avoid Windows-centric language (e.g., refer to 'command-line' or 'shell' rather than 'PowerShell' when discussing general concepts).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-planning.md ...n/articles/storage/elastic-san/elastic-san-planning.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Reference
Summary
The documentation page exhibits mild Windows bias. In the encryption section, BitLocker (a Windows-specific tool) is referenced as an analogy for storage service encryption, and the only deep-dive link for cryptographic modules is to a Windows-specific API (Cryptography API: Next Generation). In the networking section, mounting instructions mention AKS, Linux, and Windows, but Windows is listed last, which is not biased. However, there are no command-line examples or tooling references for either platform, so there is no overt PowerShell or CLI bias. Overall, the documentation leans on Windows concepts and references for explanations and further reading, which may not be as relatable for Linux users.
Recommendations
  • When using analogies for encryption, include Linux equivalents (e.g., 'similar to BitLocker on Windows or LUKS on Linux').
  • Provide links to cross-platform or Linux-specific cryptographic documentation (e.g., dm-crypt, LUKS, or general AES/FIPS documentation) alongside Windows references.
  • Ensure that any tooling or API references are balanced, or at least mention Linux alternatives if Windows-specific tools are cited.
  • If examples or scripts are added in the future, ensure parity between Windows (PowerShell, etc.) and Linux (bash, etc.) examples.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-replace-drive.md .../articles/storage/file-sync/file-sync-replace-drive.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric. All examples use Windows-only tools (Robocopy), reference Windows services (Storage Sync Agent Service), and assume the use of Windows Server. There are no Linux equivalents or instructions, and no mention of how to perform these tasks on Linux systems or with cross-platform tools.
Recommendations
  • Add equivalent instructions for Linux servers, including supported distributions and any prerequisites.
  • Provide examples using cross-platform tools (e.g., rsync for file copying) alongside Robocopy.
  • Clarify whether Azure File Sync is supported on Linux, and if not, explicitly state this early in the documentation.
  • If only Windows is supported, add a prominent note to avoid confusion for Linux administrators.
  • Where possible, use neutral terminology (e.g., 'copy files using your platform's preferred tool') and provide both Windows and Linux command examples.
  • Document how to manage SMB access and sync agent services on Linux, if supported.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-analytics-logging.md ...n/articles/storage/common/storage-analytics-logging.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is the only scripting example provided for interacting with logs, and no equivalent Azure CLI, Bash, or Linux-native example is given. The sample log entries and user agent strings repeatedly reference Windows-specific tools and platforms (e.g., 'win32', 'Windows_NT'), and Windows tools are mentioned before or instead of cross-platform alternatives. There is no guidance or example for Linux or macOS users for common tasks such as filtering blobs or viewing metadata.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples alongside PowerShell snippets for tasks such as filtering blobs and reading metadata.
  • Include references to cross-platform tools (e.g., Azure Storage Explorer for Linux/macOS, AzCopy on Linux) and show their usage.
  • When mentioning tools or user agents, clarify their cross-platform availability and provide examples relevant to Linux/macOS environments.
  • Ensure that instructions and code samples are not Windows-centric by default; present cross-platform or Linux-first examples where appropriate.
  • Explicitly state that all features and operations are available on Linux/macOS, and link to relevant documentation for those platforms.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/manage-storage-analytics-logs.md ...ticles/storage/common/manage-storage-analytics-logs.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based CLI examples for scripting and automation, explicitly instructing users to open a Windows PowerShell command window. There are no equivalent examples for Linux users (e.g., Bash, Azure CLI), and file paths in AzCopy examples use Windows-style paths. The documentation refers to Windows tools and patterns before or instead of cross-platform or Linux-native alternatives.
Recommendations
  • Provide equivalent Azure CLI (az) examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Avoid instructions that explicitly reference 'Windows PowerShell command window'; instead, use neutral language like 'open a terminal window'.
  • When showing file paths (e.g., in AzCopy examples), include both Windows and Linux/macOS path formats, or use placeholders and explain both.
  • Mention and demonstrate the use of cross-platform tools (e.g., Azure CLI, AzCopy) equally alongside PowerShell.
  • If referencing Microsoft Azure Storage Explorer, clarify its cross-platform availability.
  • Add Bash or shell script examples where appropriate, especially for common administrative tasks.
  • Ensure that any .NET code samples are supplemented with samples for other languages commonly used on Linux, where possible.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-agent-silent-installation.md ...orage/file-sync/file-sync-agent-silent-installation.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides instructions and examples for installing the Azure File Sync agent on Windows, using Windows-specific tools (msiexec), Windows file paths, and Windows environment variables. There are no references to Linux, Linux tools, or cross-platform installation methods, indicating a strong Windows bias.
Recommendations
  • Explicitly state if Azure File Sync agent is only supported on Windows. If so, clarify this early in the documentation to set user expectations.
  • If Linux support is planned or available, provide equivalent Linux installation instructions, including command-line examples (e.g., using dpkg, rpm, or shell scripts).
  • Include Linux file path examples and environment variable formats where relevant.
  • If the agent is Windows-only, consider linking to alternative Azure file synchronization solutions for Linux environments.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for Azure File Sync demonstrates a strong Windows bias. All examples, scenarios, and deployment instructions exclusively reference Windows Server, with no mention of Linux or cross-platform alternatives. The language assumes the use of Windows Server for local caching, management, and recovery, and only Windows-specific tools and protocols are discussed in detail.
Recommendations
  • Explicitly state whether Azure File Sync supports only Windows Server, or clarify any Linux or cross-platform limitations.
  • If Linux support exists or is planned, provide equivalent Linux examples and instructions for deployment, management, and recovery.
  • Mention Linux-compatible protocols (such as NFS) in parity with SMB, and clarify how non-Windows clients can interact with Azure File Sync.
  • If only Windows Server is supported, add a note early in the documentation to set expectations for non-Windows users.
  • Consider including a comparison table outlining feature availability and limitations for Windows vs. Linux environments.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azurite.md ...ob/main/articles/storage/common/storage-use-azurite.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-specific tools (Visual Studio, .exe paths), using Windows-style paths (c:\azurite) in all CLI examples, and omitting explicit Linux/macOS command examples for running Azurite or specifying data directories. Installation and usage instructions for Visual Studio are Windows-centric, and there are no Linux/macOS-specific instructions or screenshots. While the introduction claims cross-platform support, practical guidance is overwhelmingly Windows-focused.
Recommendations
  • For every CLI example using Windows paths (e.g., c:\azurite), provide equivalent Linux/macOS examples (e.g., /home/user/azurite or ~/azurite).
  • Explicitly document the location of the Azurite executable for Visual Studio Code and npm/Docker installs on Linux/macOS.
  • Add Linux/macOS-specific instructions and screenshots where appropriate, especially for file paths, environment variables (e.g., export vs set), and Docker volume mounts (e.g., -v ~/azurite:/data).
  • Where Visual Studio is referenced, clarify that it is Windows-only and provide alternative workflows for Linux/macOS users (e.g., using VS Code, npm, or Docker).
  • Ensure that all environment variable examples include both Windows (set) and Linux/macOS (export) syntax.
  • Add a section or tab for 'Linux/macOS' in all relevant install/run instructions to ensure parity.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All examples and instructions assume the use of Windows tools (icacls, Windows File Explorer, net use), require a Windows client, and reference PowerShell cmdlets. There are no Linux or cross-platform examples, nor any mention of how to manage permissions from non-Windows systems. The documentation also assumes Active Directory integration in a Windows context and does not address Linux SMB clients or NFS scenarios.
Recommendations
  • Add instructions and examples for configuring file share permissions from Linux clients, including mounting Azure Files over SMB using Linux tools (e.g., mount.cifs) and managing permissions with setfacl or equivalent.
  • Clarify whether Windows ACLs can be managed from non-Windows clients, and if not, explicitly state this limitation.
  • If Azure Files does not support Linux ACLs or NFS permissions, mention this clearly and provide guidance for Linux/NFS users.
  • Include parity in documentation structure: present Linux (and macOS, if supported) options alongside Windows, not just as an afterthought.
  • Reference cross-platform tools or APIs (such as Azure CLI, REST API, or AzCopy) where possible for managing permissions, and provide examples for their use on Linux.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-client-version.md ...n/transport-layer-security-configure-client-version.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by providing configuration examples only for PowerShell and .NET (both Windows-centric), referencing Fiddler (a Windows tool) for verification, and omitting any Linux or cross-platform command-line examples. There is no mention of Linux shell commands, OpenSSL, or Linux-native tools for TLS configuration or verification.
Recommendations
  • Add equivalent examples for configuring TLS version in common Linux environments, such as using curl or Python scripts.
  • Include instructions or code samples for verifying TLS version on Linux, e.g., using tcpdump, Wireshark, or OpenSSL.
  • Mention and demonstrate cross-platform tools for network traffic inspection, such as Wireshark or tcpdump, alongside or instead of Fiddler.
  • Ensure that examples and tool recommendations are presented in a platform-neutral order, or provide parallel Windows and Linux/macOS instructions.
GitHub Create Pull Request
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is exclusively focused on Windows environments, both in prerequisites and all example commands. It explicitly states that Azure File Sync is only supported on Windows, and all instructions, settings, and validation steps are tailored for Windows servers. There are no Linux equivalents, examples, or even mentions of Linux support or alternatives. All tooling and patterns (e.g., PowerShell, Windows file paths, Windows services) are Windows-centric, and Linux is only mentioned to clarify lack of support.
Recommendations
  • If Azure File Sync is not supported on Linux, clearly state this at the top and consider providing links to alternative solutions for Linux file sync scenarios (e.g., Azure File NFS, rsync, third-party tools).
  • If Linux support is planned or possible in the future, add a section outlining current limitations and a roadmap or workaround for Linux users.
  • Where possible, generalize Azure CLI examples to clarify which steps are cross-platform, and explicitly note which commands or features are Windows-only.
  • Provide a comparison table or FAQ addressing common Linux administrator questions (e.g., 'What should I use if I have Linux servers?').
  • Avoid using Windows-specific terminology (like C:\ paths, Programs and Features, FileSyncSvc) in generalized sections, or clearly scope them as Windows-only.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-encrypt-decrypt-blobs-key-vault.md ...orage/blobs/storage-encrypt-decrypt-blobs-key-vault.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows, such as Visual Studio and PowerShell, and by presenting Windows-specific instructions before Linux equivalents. PowerShell and Windows command-line examples are given prominence, while Linux alternatives are sometimes less detailed or appear after Windows instructions. There is also a focus on Windows development environments, with Visual Studio as the primary editor, and some steps (like package installation) include PowerShell-specific tabs but lack equivalent coverage for Linux-native tools (e.g., apt, yum, or .NET CLI on Linux).
Recommendations
  • Present Linux and Windows instructions in parallel or give equal prominence to both, avoiding 'Windows first' ordering.
  • Include Linux-native tooling and workflows (e.g., .NET CLI on Linux, common editors like Vim or nano, and package managers like apt or yum where relevant).
  • Provide Bash and PowerShell examples side by side for all command-line operations.
  • Reference cross-platform editors (such as VS Code) before or alongside Windows-only editors like Visual Studio.
  • Ensure that all steps (such as setting environment variables, installing packages, and assigning roles) have clear, tested Linux equivalents.
  • Avoid assuming the use of Windows-specific tools (like PowerShell) as the default for scripting or automation.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-configure.md ...rticles/storage/common/storage-use-azcopy-configure.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias: Windows and PowerShell examples are consistently presented first, and Windows-specific tools and environment variable syntax (PowerShell, cmd.exe) are described in greater detail or before Linux/macOS equivalents. Linux and macOS are included, but often as secondary considerations.
Recommendations
  • Alternate the order in which Windows and Linux/macOS examples are presented, or present them side-by-side to avoid prioritizing one platform.
  • Provide equal detail for Linux/macOS shell usage (e.g., mention Bash or zsh explicitly, not just 'Linux').
  • When discussing quoting or environment variables, clarify the shell context for each OS (e.g., Bash for Linux/macOS, PowerShell and cmd.exe for Windows) and provide parallel examples.
  • Include a general, platform-agnostic example first, followed by OS-specific notes if needed.
  • Avoid using Windows-specific terminology (like %USERPROFILE%) without immediately providing the Linux/macOS equivalent in the same sentence.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-mount-file-share.md ...orage/files/storage-files-identity-mount-file-share.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All mounting instructions, code samples, and troubleshooting steps are exclusively for Windows environments, using Windows-specific tools (PowerShell, net use, setspn, Active Directory DNS Manager). There are no examples, commands, or guidance for mounting Azure SMB file shares from Linux or macOS clients, nor is there mention of Linux authentication patterns or tools.
Recommendations
  • Add a dedicated section for mounting Azure SMB file shares from Linux clients, including examples using the 'mount.cifs' command and relevant authentication options.
  • Provide Linux-specific prerequisites, such as required packages (e.g., cifs-utils), and guidance on Kerberos configuration for identity-based access.
  • Include troubleshooting steps and links relevant to Linux environments.
  • Mention macOS support or limitations, if applicable.
  • Ensure that examples for both Windows and Linux are presented in parallel or with equal prominence, rather than Windows-first.
  • Reference cross-platform tools and patterns where possible, and clarify any Windows-only limitations.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-best-practices.md ...cles/storage/elastic-san/elastic-san-best-practices.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Windows examples and tools (such as PowerShell and Registry Editor) are often presented first or in more detail, and Windows-specific tools (e.g., iSCSI Initiator app, PowerShell cmdlets) are referenced directly. Linux examples are present and reasonably detailed, but Windows workflows and screenshots are prioritized or described before Linux equivalents.
Recommendations
  • Alternate the order of Windows and Linux sections/examples throughout the document to avoid always listing Windows first.
  • Where possible, provide equal detail and step-by-step instructions for both Windows and Linux, including screenshots for both platforms.
  • Reference Linux-native tools (e.g., iscsiadm, multipath-tools) as prominently as Windows tools, and provide links to their documentation.
  • When mentioning PowerShell or Windows-specific tools, also mention the equivalent Linux commands or configuration files in the same context.
  • Ensure that any Azure CLI instructions are cross-platform and not only PowerShell-focused.
  • Consider adding a summary table or section at the start that outlines parity and differences between Windows and Linux workflows.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-minimum-version.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-minimum-version.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and patterns. PowerShell is given a dedicated section before the cross-platform Azure CLI, and there is a notable emphasis on the Azure portal (which is platform-agnostic but often associated with Windows workflows). Additionally, the documentation references Windows-specific implementation details (such as Azure Storage relying on the Windows SSL stack) and links to Application Gateway configuration via PowerShell. There are no explicit Linux-specific examples or mentions of Linux command-line tools, and the documentation does not address any platform-specific considerations for Linux users.
Recommendations
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Include explicit Linux shell (bash) usage examples where relevant, especially for scripting or automation tasks.
  • When referencing tools or configuration steps (such as Application Gateway SSL policy), provide both PowerShell and Azure CLI (or ARM template) instructions.
  • Clarify that the Azure portal and Azure CLI are fully supported on Linux, and mention any platform-specific caveats if they exist.
  • Avoid language that implies Windows is the default or preferred platform (e.g., by stating 'Azure Storage relies on Windows implementation of SSL...') without balancing with Linux/OpenSSL context.
  • Add a section or note for Linux users, highlighting any differences or confirming parity in functionality and tooling.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-networking-dns.md ...articles/storage/files/storage-files-networking-dns.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell cmdlets (e.g., Add-DnsServerConditionalForwarderZone, Resolve-DnsName, Test-NetConnection), and prerequisites specifically mention the Azure PowerShell module. The instructions assume the use of Windows Server DNS, and there are no examples or guidance for configuring DNS forwarding using Linux-based DNS servers (such as BIND or dnsmasq). Linux tools and workflows are not mentioned, and no Linux command-line equivalents are provided.
Recommendations
  • Add equivalent Linux-based DNS server configuration steps (e.g., using BIND or dnsmasq) for conditional forwarding.
  • Provide Linux command-line examples for DNS testing (e.g., dig, nslookup) alongside PowerShell examples.
  • Mention Linux DNS server options explicitly in the prerequisites and guidance, not just Windows Server DNS.
  • Where possible, present cross-platform instructions or clearly separate Windows and Linux sections.
  • Reference relevant Linux documentation or external resources for configuring DNS forwarding on popular distributions.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/queues-storage-monitoring-scenarios.md .../storage/queues/queues-storage-monitoring-scenarios.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell examples before Azure CLI, focusing on .NET (C#) SDK code, and omitting explicit Linux/bash or cross-platform scripting examples. There are no Linux-specific command-line examples (e.g., Bash, shell scripts), and the tools and workflows highlighted (PowerShell, .NET) are more familiar to Windows users.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell and Azure CLI, especially for common monitoring tasks.
  • Include code samples using cross-platform SDKs (e.g., Python, JavaScript) in addition to .NET/C#.
  • Alternate the order of examples so that Azure CLI or Bash appears before or alongside PowerShell to avoid a 'Windows-first' impression.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary Linux-specific notes (e.g., quoting, authentication).
  • Where screenshots or portal instructions are given, clarify that the Azure portal is accessible from any OS.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-configure-service-endpoints.md ...elastic-san/elastic-san-configure-service-endpoints.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents PowerShell (a Windows-centric tool) examples before Azure CLI examples, and uses PowerShell variable syntax in CLI examples. There is a notable emphasis on PowerShell scripts and terminology, which may be less familiar or accessible to Linux users. No native Linux shell (bash) or cross-platform scripting examples are provided, and there is no mention of Linux-specific tools or workflows. The documentation assumes familiarity with Windows/PowerShell patterns, which can create friction for Linux users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (which is cross-platform) examples first.
  • Use bash-style variable syntax in Azure CLI examples (e.g., RgName="<ResourceGroupName>") instead of PowerShell-style ($RgName).
  • Explicitly state that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Where possible, provide bash script examples for Linux users, especially in sections that involve scripting or automation.
  • Avoid exclusive references to Windows tools or patterns; ensure parity in instructions and terminology for both Windows and Linux environments.
  • Add a brief section or note on how to install and use Azure CLI and PowerShell on Linux, highlighting cross-platform support.
GitHub Create Pull Request
← Previous Page 32 of 67 Next →