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 851-875 of 1657 flagged pages
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/primary-secondary-storage/isv-file-services.md ...artners/primary-secondary-storage/isv-file-services.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias, primarily through the mention of Windows-specific tools and environments (e.g., Windows Server, Windows file servers, Windows Shell integration) and by highlighting Windows-centric features (such as NTFS tiering and Windows clustering) without equivalent Linux examples or parity. Some ISV solutions are described as operating specifically on Windows Server, and features like Windows Shell integration are called out, while Linux environments, tools, or integration points are not mentioned or are less visible. There are no explicit Linux command-line or management examples, and Linux-based deployment or management patterns are not discussed.
Recommendations
  • For each ISV solution that highlights Windows Server or Windows-specific features, add equivalent information for Linux environments if supported (e.g., Linux-based file servers, Linux clustering, Linux shell integration).
  • Where features like 'Windows Shell integration' are mentioned, clarify if there are Linux desktop or CLI equivalents, or explicitly state if such features are unavailable on Linux.
  • If a solution is Windows-only, clearly state this; if Linux is supported, provide parity in feature descriptions and management tooling.
  • Include Linux-focused deployment, management, and failover patterns/examples where relevant, such as using Linux VMs, Linux clustering, or Linux-native file systems.
  • Add explicit Linux compatibility notes or examples in tables, especially in the 'Operating Environment' and 'Automatic failover' sections.
  • Where NTFS or Windows file server is referenced, mention Linux file systems (e.g., ext4, XFS) or NFS server options if supported.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/primary-secondary-storage/tiger-bridge-deployment-guide.md ...ary-secondary-storage/tiger-bridge-deployment-guide.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 demonstrates a strong Windows bias. It assumes deployment on Windows Server, references NTFS/ReFS file systems, and requires a Windows file server for installation. All setup and configuration steps, screenshots, and features (such as the Windows Explorer shell extension) are Windows-centric. There are no Linux-specific instructions, examples, or screenshots, and no mention of Linux-native deployment, tools, or command-line equivalents.
Recommendations
  • Add explicit instructions and examples for deploying Tiger Bridge on Linux-based systems, if supported, including supported file systems (e.g., ext4, XFS) and integration with NFS/SMB exports.
  • Provide Linux command-line examples (e.g., bash, shell scripts) for installation, configuration, and management, alongside or instead of Windows GUI and PowerShell instructions.
  • Include screenshots or terminal output from Linux environments to illustrate cross-platform parity.
  • Clarify in the introduction and prerequisites whether Tiger Bridge can be installed natively on Linux, or only as a gateway to NAS devices, and provide guidance for Linux users accordingly.
  • Mention Linux-native tools for bandwidth and network monitoring (e.g., iftop, nload, vnStat, Netdata) alongside the Windows/third-party tools listed.
  • If Linux is not supported for direct Tiger Bridge installation, explicitly state this limitation early in the documentation and provide alternative architectures or partner solutions for Linux environments.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/data-management/storagex-quick-start-guide.md ...partners/data-management/storagex-quick-start-guide.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 demonstrates a Windows bias by focusing on Windows-centric deployment and operational patterns. It assumes the use of Active Directory, Windows file servers, and Windows-based tools (e.g., portqryui), and provides detailed steps and screenshots for Windows environments. There is a lack of equivalent Linux/NFS-focused examples, commands, or guidance, and Linux-native tools or patterns are not mentioned or are only referenced in passing.
Recommendations
  • Provide parallel Linux/NFS deployment instructions, including how to deploy and configure StorageX on Linux-based systems if supported.
  • Include examples and screenshots for NFS migrations, not just SMB/Windows/Active Directory scenarios.
  • Mention and provide usage examples for Linux-native tools (e.g., netcat, ss, iperf, or nmap) for port and bandwidth testing, alongside or instead of Windows tools like portqryui.
  • Clarify whether StorageX requires Windows for deployment, or if Linux-based deployments are possible, and document any differences.
  • Ensure that instructions for creating service accounts and setting permissions include Linux/NFS equivalents (e.g., export rules, root squash, POSIX permissions), not just Active Directory/Windows group memberships.
  • Balance the order of presentation so that NFS/Linux scenarios are given equal prominence to SMB/Windows ones, rather than always following or being secondary.
  • Add troubleshooting and support guidance for Linux/NFS environments, not just Windows/Active Directory.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/tables/storage-performance-checklist.md ...ticles/storage/tables/storage-performance-checklist.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows-specific tools (e.g., WireShark, NetMon), focusing on .NET Framework (primarily used on Windows), and mentioning PowerShell before Azure CLI. There are no explicit Linux or cross-platform command-line examples, and configuration/code snippets are .NET/C#-centric, with no parity for Linux or non-Windows environments.
Recommendations
  • When mentioning diagnostic tools, include popular Linux alternatives (e.g., tcpdump, Wireshark for Linux, or iperf) alongside Windows tools like NetMon.
  • Provide code/configuration examples for other languages and platforms (e.g., Python, Java, Node.js) and reference their connection/thread pool management.
  • When referencing Azure CLI and PowerShell, mention Azure CLI first or equally, as it is cross-platform, and provide example commands for both.
  • Explicitly state that the guidance applies to both Windows and Linux clients where relevant, and highlight any OS-specific considerations.
  • Where .NET Framework is discussed, also mention .NET Core/.NET 5+ and clarify cross-platform support.
  • Add a section or callouts for Linux/macOS users, especially in areas discussing client-side configuration or troubleshooting.
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-12 23:44
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 presented as a primary scripting example, and Azure Storage Explorer (a Windows-centric tool) is emphasized. In several places, Windows tools or workflows are mentioned before cross-platform or Linux-native alternatives. While Azure CLI is included, there are no explicit Linux shell (bash) or scripting examples, and the documentation does not reference Linux-specific tools or workflows.
Recommendations
  • Add explicit bash/shell scripting examples for Linux users, especially for common tasks such as updating storage account properties.
  • When listing tools (e.g., Azure Storage Explorer, AzCopy), clarify cross-platform availability and provide parity in instructions for Linux/macOS where possible.
  • Avoid presenting PowerShell before Azure CLI or treat both equally, as Azure CLI is more universally available across platforms.
  • Include references or links to Linux/macOS installation and usage guides for all mentioned tools.
  • Where screenshots or UI walkthroughs are shown, note any differences for Linux/macOS users or provide alternative visuals if the experience differs.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/customer-managed-keys-configure-cross-tenant-existing-account.md ...r-managed-keys-configure-cross-tenant-existing-account.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation presents PowerShell examples before Azure CLI, and the PowerShell section is detailed, which may indicate a Windows-first or PowerShell-heavy bias. There are no explicit Linux/bash shell examples, nor are there references to Linux-specific tools or workflows. While Azure CLI is cross-platform, the lack of explicit Linux shell (bash) or script examples, and the ordering of PowerShell before CLI, may disadvantage Linux users.
Recommendations
  • Add explicit bash/Linux shell examples, especially for CLI commands, including variable setting and command usage in bash syntax.
  • Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform and more familiar to Linux users.
  • Clarify in the documentation that Azure CLI commands are supported on Linux, macOS, and Windows, and provide any OS-specific notes if relevant.
  • If possible, include troubleshooting or environment setup notes for Linux users (e.g., package dependencies, shell differences).
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a clear Windows bias by exclusively providing instructions and screenshots for Visual Studio on Windows, requiring the use of Windows as the operating system for the Function App, and omitting any guidance for Linux or cross-platform development environments. There are no examples or instructions for developing, running, or publishing Azure Functions using Linux, macOS, or cross-platform tools such as VS Code, Azure CLI, or the Azure Functions Core Tools.
Recommendations
  • Add parallel instructions for developing and publishing Azure Functions using cross-platform tools such as Visual Studio Code, Azure CLI, and Azure Functions Core Tools.
  • Include guidance for creating Function Apps with Linux as the operating system, and clarify that Azure Functions can run on both Windows and Linux.
  • Provide examples and screenshots for Linux and macOS environments, including terminal commands for package installation and function deployment.
  • Mention and link to documentation for non-Windows development workflows early in the article, not just as a footnote.
  • Ensure that prerequisites and tooling sections highlight cross-platform options equally, rather than focusing solely on Visual Studio for Windows.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently mentioning PowerShell before Azure CLI, grouping them together as primary command-line interfaces, and not providing explicit Linux-specific examples or guidance. The focus on PowerShell, a Windows-centric tool, and the absence of Linux shell or scripting examples may make the documentation less approachable for Linux users.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside PowerShell and Azure CLI, especially for common tasks such as authentication and data access.
  • When listing command-line options, alternate the order or present Azure CLI (which is cross-platform) before PowerShell to avoid the appearance of Windows-first bias.
  • Include a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
  • Where possible, link to or embed examples using native Linux tools (e.g., curl, wget) for REST API calls.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, to encourage non-Windows users.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-upload-function-trigger.md ...articles/storage/blobs/blob-upload-function-trigger.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias by requiring Visual Studio 2022 (a Windows-centric IDE) as a prerequisite, providing detailed deployment instructions only for Visual Studio (with no mention of VS Code, CLI, or cross-platform alternatives), and referencing 'Azure Function App (Windows)' before 'Azure Function App (Linux)' in deployment steps. There are no explicit Linux or macOS-specific instructions or troubleshooting tips, and no mention of common Linux tools or workflows. The only command-line examples use Azure CLI, which is cross-platform, but all local development and deployment guidance is centered on Windows tools.
Recommendations
  • Add instructions for using Visual Studio Code and the Azure Functions Core Tools for local development and deployment, which are cross-platform.
  • Include explicit steps for Linux and macOS users, such as installing prerequisites, setting environment variables, and deploying via CLI.
  • Provide alternative deployment methods (e.g., Azure CLI, GitHub Actions, or VS Code) alongside Visual Studio instructions.
  • When listing deployment targets, mention 'Azure Function App (Linux)' before or alongside 'Windows' to avoid Windows-first ordering.
  • Add troubleshooting notes or tips for common Linux/macOS issues (e.g., file permissions, path differences).
  • Clarify that Visual Studio is not required and that the sample project can be built and deployed using .NET CLI and other cross-platform tools.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. In tool tables and guidance, Windows-centric tools such as Azure PowerShell and Azure Storage Explorer are consistently listed before cross-platform or Linux-native alternatives like Azure CLI. PowerShell is mentioned frequently as a primary scripting interface, and Windows tools (e.g., Azure Storage Explorer) are highlighted without equal emphasis on Linux-native equivalents. There are no explicit Linux-only examples or references to Linux shell scripting, and the documentation does not provide parity in example commands or workflows for Linux users.
Recommendations
  • Ensure that Azure CLI examples are presented alongside or before PowerShell examples, especially in tables and code samples.
  • Include Linux shell (bash) command examples for common tasks, such as data ingestion, file management, and monitoring.
  • Highlight cross-platform tools (e.g., AzCopy, Azure CLI) as primary options, and clarify their availability on Linux, macOS, and Windows.
  • Where PowerShell is mentioned, provide equivalent bash or shell script snippets for Linux users.
  • Mention and link to Linux-native tools or workflows where applicable (e.g., using curl with REST APIs, or scripting with Python).
  • In tool tables, alternate the order of Windows and Linux tools, or group them by platform to avoid implicit prioritization.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-events.md ...ain/articles/storage/blobs/data-lake-storage-events.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by specifying Windows as the operating system for the Azure Function App, omitting Linux as an option. There are no examples or instructions for Linux users, and Windows is the only OS mentioned in configuration steps. Additionally, tools like Storage Explorer are referenced without cross-platform clarification, and keyboard shortcuts or file handling instructions assume a Windows environment.
Recommendations
  • Explicitly mention that Azure Function Apps can be created on both Windows and Linux, and provide parallel instructions for Linux.
  • When listing configuration steps (such as 'Operating System'), present both Windows and Linux as valid options, or explain any differences.
  • If using tools like Storage Explorer, clarify their cross-platform availability and provide links or notes for Linux installation.
  • Include Linux-friendly instructions for file creation, editing, and uploading (e.g., using nano, vim, or Linux file managers).
  • Avoid defaulting to Windows terminology (e.g., 'SHIFT + ENTER' is fine, but clarify that it applies to all OSes).
  • Where screenshots or UI steps are shown, note any differences for Linux users if applicable.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-known-issues.md ...ticles/storage/blobs/data-lake-storage-known-issues.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell and Windows-specific tools (such as WASB) without providing equivalent Linux or cross-platform examples. In the section on restoring soft-deleted blobs, only PowerShell and Azure CLI are mentioned, but no explicit Linux shell or Bash examples are provided. The WASB driver is discussed without clarifying its Windows-centric nature or offering Linux alternatives up front. There is a lack of parity in tool and example coverage for Linux users.
Recommendations
  • Provide explicit Bash or Linux shell examples alongside PowerShell and Azure CLI commands, especially in sections like soft delete restoration.
  • Clarify when tools or drivers (such as WASB) are Windows-specific, and always mention Linux or cross-platform alternatives (such as ABFS) with equal prominence.
  • When referencing Azure CLI, include both Windows (PowerShell/CMD) and Linux (Bash) command syntax where they differ.
  • Add a section or table summarizing tool and driver support across platforms (Windows, Linux, macOS) to help users quickly identify the best option for their environment.
  • Review all instructions and examples to ensure Linux users are not required to infer steps from Windows-centric guidance.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/lifecycle-management-policy-configure.md ...storage/blobs/lifecycle-management-policy-configure.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and command breakdowns, while the Azure CLI (cross-platform) section is less detailed and only provides a single command. PowerShell is presented before Azure CLI, and the documentation references Windows-centric tools and patterns (PowerShell cmdlets) without offering equivalent Linux shell or scripting examples. There are no explicit Linux/Unix shell examples or references to Linux-specific workflows.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell, especially for tasks like preparing the JSON policy file and invoking the Azure CLI.
  • Reorder the command-line sections so that Azure CLI (cross-platform) appears before PowerShell, or present both in parallel tabs.
  • Expand the Azure CLI section to include more detailed, step-by-step instructions, similar to the PowerShell section (e.g., how to construct the JSON policy, how to edit it, and how to validate the policy).
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
  • Where possible, avoid Windows-specific terminology or tools unless there is no cross-platform equivalent, and always provide parity in examples.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references PowerShell as a method for enabling static websites, mentions Windows client limitations before Linux, and provides a workaround for Windows users (via WSL 2) without offering equivalent Linux-native guidance or examples. There are no explicit Linux command-line examples or instructions, and the only workaround for Windows is to use a Linux environment (WSL 2), implying a Windows-centric audience. The mention of PowerShell before Azure CLI also prioritizes Windows tooling.
Recommendations
  • Provide explicit Linux-native examples for mounting NFS 3.0 shares, including common distributions and mount commands.
  • When referencing tooling (e.g., enabling static websites), mention Azure CLI and Linux shell commands before or alongside PowerShell.
  • Add a section or examples for Linux and macOS users, not just Windows/WSL 2.
  • Balance the order of presenting Windows and Linux tools to avoid implying Windows primacy.
  • Include troubleshooting steps or known issues specific to Linux clients, not just Windows.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured heavily, with detailed examples and instructions, and file paths in PowerShell examples use Windows-style (C:\temp\...). There is no mention of Linux shell equivalents (e.g., Bash scripts), and PowerShell is presented as a primary automation tool, which is more native to Windows. In some cases, PowerShell examples appear before Azure CLI, and there is no explicit guidance for Linux users regarding file paths or shell usage.
Recommendations
  • Add Bash shell script examples alongside PowerShell for all CLI-based workflows, especially for tasks like file manipulation and scripting.
  • Use platform-neutral file paths in examples (e.g., ./policy.json instead of C:\temp\json.txt), or provide both Windows and Linux/Mac path examples.
  • Explicitly mention that Azure CLI commands work cross-platform and, where relevant, show how to run them in Bash or other common Linux shells.
  • When presenting PowerShell and Azure CLI, alternate the order or clarify that both are equally supported, to avoid the impression of Windows-first bias.
  • Where PowerShell-specific instructions are given (e.g., module installation), provide Linux equivalents or note any differences in usage on Linux/Mac.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-support-connect.md ...blobs/secure-file-transfer-protocol-support-connect.md
High Priority View Details →
Scanned: 2025-07-12 23:44
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 providing its only explicit SFTP connection example in a Windows PowerShell session, referencing Windows-specific documentation, and omitting equivalent Linux/macOS command-line examples. This may make Linux users feel less supported or require them to infer the correct usage for their platforms.
Recommendations
  • Add a Linux/macOS example alongside the Windows PowerShell example, e.g., showing the sftp command in a bash shell.
  • Reference both Windows and Linux OpenSSH documentation, or provide a neutral link to OpenSSH's official site.
  • Rephrase the introductory example to clarify that the sftp command works similarly on all platforms, and that the example shown is just one possible environment.
  • Consider providing a table or section listing common SFTP clients and usage patterns for Windows, Linux, and macOS.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed PowerShell examples and instructions for Azure Data Lake Storage query acceleration, but does not offer equivalent command-line examples for Linux or cross-platform shells (e.g., Bash, Azure CLI). The PowerShell sections are present throughout, and installation/setup steps reference Windows-centric tools (PowerShell, Az module) without Linux alternatives. There are no Bash, Azure CLI, or Linux shell script examples, and no mention of Linux-specific tools or patterns.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell code snippets, demonstrating how to perform the same operations from Bash or other cross-platform shells.
  • Include instructions for installing and using the Azure CLI on Linux/macOS in the prerequisites and setup sections.
  • Where PowerShell is referenced, clarify that it is available cross-platform, or provide Bash alternatives where possible.
  • Ensure that any references to temporary file creation, file manipulation, or scripting are also shown using Linux shell commands (e.g., mktemp, cat, etc.).
  • Consider adding a 'Linux/macOS' or 'Bash' tab alongside the existing PowerShell tab for parity.
  • Explicitly mention that the SDK examples (.NET, Java, Python, Node.js) are cross-platform, and provide any necessary Linux-specific notes (e.g., package installation commands for apt/yum/pip).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/point-in-time-restore-manage.md ...articles/storage/blobs/point-in-time-restore-manage.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting PowerShell examples and instructions before Azure CLI, and by providing detailed PowerShell command usage. PowerShell, a Windows-centric tool, is highlighted as a primary automation method, which may disadvantage Linux users. There are no Linux shell-specific examples (e.g., Bash), and the documentation does not mention Linux tools or patterns. While Azure CLI is cross-platform, the ordering and emphasis favor Windows/PowerShell users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI first to reflect its cross-platform nature.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh).
  • Add Bash script examples for common workflows, especially for automation scenarios.
  • Clarify that PowerShell Core is available cross-platform, but note that most Linux users will prefer Azure CLI or Bash.
  • Where screenshots or UI references are provided, ensure they are not Windows-specific (e.g., avoid showing only Windows-style terminals).
  • Consider including a brief section on using REST API directly, which is platform-agnostic.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page presents monitoring instructions for Azure Blob Storage with a clear ordering and example bias: PowerShell is given as the first command-line example, and detailed PowerShell scripts are provided before Azure CLI examples. There are no explicit Linux shell (bash) examples, and no mention of Linux-specific tools or patterns. The .NET SDK example is platform-neutral but is more familiar to Windows developers. There are no references to Linux-native scripting, nor are there any screenshots or walkthroughs from a Linux perspective.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
  • Include bash shell script examples for common monitoring tasks, demonstrating how to use Azure CLI in a Linux environment.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary setup instructions for Linux users.
  • Add references or links to Linux-native monitoring tools (e.g., integration with syslog, or using jq for JSON parsing of CLI output).
  • Ensure screenshots and UI walkthroughs are not Windows-centric (e.g., avoid showing only Windows-style file paths or PowerShell terminals).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/quickstart-blobs-c-plus-plus.md ...articles/storage/blobs/quickstart-blobs-c-plus-plus.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows-first bias, particularly in the project setup and tooling sections. Visual Studio and .sln files are presented as the default development environment, with screenshots and instructions specific to Windows. The initial vcpkg install command uses the Windows-style executable (vcpkg.exe), and project creation is described only for Visual Studio on Windows, with no mention of Linux or cross-platform alternatives. While environment variable setup is shown for both Windows and Linux, Linux development environments and editors are not discussed, and Linux-specific build instructions are missing.
Recommendations
  • Provide parallel instructions for setting up and building the project on Linux, including using CMake and common Linux editors (e.g., VS Code, CLion, or command-line tools).
  • Show vcpkg usage with platform-agnostic commands (e.g., './vcpkg install ...') or clarify the difference for Windows and Linux.
  • Include screenshots or instructions for creating a C++ project using cross-platform tools or Linux IDEs.
  • Mention how to open, build, and run the project on Linux, including any differences in file structure or build commands.
  • Ensure all code snippets and setup steps are clearly marked for both Windows and Linux where they differ.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/simulate-primary-region-failure.md ...icles/storage/blobs/simulate-primary-region-failure.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a moderate Windows bias. While the static route simulation provides both Windows and Linux command examples, the Fiddler-based failure simulation only references Fiddler, a Windows-centric tool, with no mention of Linux or cross-platform alternatives. Additionally, the Fiddler method is presented as a primary approach alongside static routing, potentially disadvantaging Linux users. In some instructions, Windows commands or tools (e.g., 'ipconfig') are mentioned before their Linux equivalents.
Recommendations
  • Include a cross-platform alternative to Fiddler for simulating HTTP failures, such as mitmproxy or similar tools, and provide equivalent Linux/macOS instructions.
  • When listing commands or tools, present Linux and Windows options in parallel or alternate their order to avoid Windows-first bias.
  • Explicitly state platform limitations for tools like Fiddler and suggest open-source or native alternatives for non-Windows users.
  • Ensure all major steps and troubleshooting sections have both Windows and Linux/macOS examples where applicable.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-support.md ...storage/blobs/secure-file-transfer-protocol-support.md
High Priority View Details →
Scanned: 2025-07-12 23:44
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 providing SFTP connection examples using PowerShell syntax and referencing Windows-specific tools (such as OpenSSH for Windows) without offering equivalent Linux/macOS command-line examples. The only SFTP command-line examples are shown in PowerShell code blocks, and the only explicit client walkthrough is for OpenSSH on Windows. There is no mention or example of using native Linux/macOS SFTP clients, nor are Linux-specific tools or workflows discussed. This may make the documentation less accessible or immediately useful to Linux/macOS users.
Recommendations
  • Provide SFTP connection examples using standard Linux/macOS shell syntax (e.g., bash), alongside or instead of PowerShell.
  • Include explicit references to native Linux/macOS SFTP clients and workflows, such as the default 'sftp' command or 'scp' on Unix-like systems.
  • Ensure that code blocks are marked appropriately for the shell being used (e.g., 'bash' instead of 'powershell' when showing cross-platform commands).
  • Mention that the SFTP protocol and commands are cross-platform, and clarify any platform-specific differences if relevant.
  • Where Windows-specific tools are referenced (e.g., OpenSSH for Windows), also reference their Linux/macOS equivalents.
  • Consider adding a section or callout for Linux/macOS users, summarizing any differences or additional steps required.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/soft-delete-container-enable.md ...articles/storage/blobs/soft-delete-container-enable.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell instructions (a Windows-centric tool) before Azure CLI examples, and does not include any explicit Linux or Bash-specific guidance. The PowerShell section is more extensive and comes before the cross-platform Azure CLI, which may disadvantage Linux/macOS users. There are no Linux-specific examples or notes, and the template and portal instructions are platform-neutral.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI commands, including any necessary authentication or environment setup steps for Linux users.
  • Reorder the command-line sections to present Azure CLI (cross-platform) before PowerShell, or clarify that Azure CLI is recommended for Linux/macOS.
  • Include notes or links for installing and using Azure CLI on Linux/macOS.
  • Where PowerShell is used, clarify that it is primarily for Windows users, and suggest alternatives for Linux/macOS.
  • Consider providing REST API or SDK examples, which are platform-agnostic, to further improve parity.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/soft-delete-blob-enable.md ...main/articles/storage/blobs/soft-delete-blob-enable.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is given equal or greater prominence than Azure CLI, and is always listed before CLI in tabbed sections. Instructions for using the Azure CLI reference opening a 'Windows PowerShell' console, and there is no explicit mention of Linux or macOS terminals. The Azure Portal is platform-agnostic, but the overall pattern and language favor Windows tools and workflows.
Recommendations
  • Alternate the order of PowerShell and Azure CLI sections, or present CLI first to avoid always privileging Windows-native tools.
  • In CLI instructions, explicitly mention that commands can be run from Bash or other Linux/macOS terminals, not just Windows PowerShell.
  • Wherever 'Windows PowerShell' is referenced as a console, add 'or a Bash terminal on Linux/macOS' to clarify cross-platform compatibility.
  • Add explicit notes or examples for Linux/macOS users where command-line instructions are given, especially for authentication and environment setup.
  • Consider including screenshots or terminal prompts that reflect both Windows and Linux environments.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-change-feed.md ...ain/articles/storage/blobs/storage-blob-change-feed.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in the 'Enable and disable the change feed' section. PowerShell is given a dedicated section with detailed, step-by-step instructions, while Linux-native tools or shell scripting are not mentioned. The Azure CLI example is present (which is cross-platform), but the PowerShell section is more elaborate and appears before the ARM template section. There are no explicit Linux shell (bash) examples or references to Linux-specific tooling or workflows. Additionally, Azure Storage Explorer and the Azure portal are mentioned as GUI tools, but there is no mention of Linux-native file system mounting or open-source alternatives.
Recommendations
  • Add explicit Linux/bash examples for enabling/disabling change feed, such as using Azure CLI in a bash shell, including authentication steps.
  • Clarify that Azure CLI commands are cross-platform and provide any Linux-specific notes if necessary (e.g., line continuation differences).
  • Consider including examples using REST API with curl or similar Linux-native tools.
  • Balance the PowerShell section with a comparable bash/Linux shell section, or at least mention parity.
  • Mention Linux-compatible tools for browsing containers (e.g., azcopy, blobfuse, or third-party open-source tools) alongside Azure Storage Explorer.
  • Avoid giving more detailed or prominent instructions for Windows/PowerShell than for Linux/bash.
GitHub Create Pull Request
← Previous Page 35 of 67 Next →