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 426-450 of 1657 flagged pages
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/immutable-version-level-worm-policies.md ...storage/blobs/immutable-version-level-worm-policies.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell commands are referenced first and in detail for control plane operations (e.g., Remove-AzRmStorageContainer), with explicit mention of PowerShell modules. Windows-centric tools and patterns (PowerShell, Azure portal) are mentioned before their Linux-friendly equivalents (Azure CLI), and no Linux-specific shell examples (bash, zsh) or cross-platform scripting are provided. There is no mention of Linux-specific tools or guidance for Linux users.
Recommendations
  • Provide Linux shell (bash) and cross-platform CLI examples alongside PowerShell commands.
  • Reference Azure CLI commands before or alongside PowerShell commands to ensure parity.
  • Clarify that all commands (PowerShell, CLI) are available on both Windows and Linux, and provide installation links for both platforms.
  • Include guidance for Linux users, such as using Azure CLI in bash or zsh, and note any platform-specific considerations.
  • Avoid assuming PowerShell as the default automation tool; present CLI and REST API options equally.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples and instructions for installing the Az PowerShell module, which is a Windows-centric tool. PowerShell is presented as a primary tab alongside SDKs, and Windows-specific tools (such as New-TemporaryFile and Get-Content) are used in examples. There is no mention of Linux shell equivalents (e.g., Bash, CLI), nor are Linux-specific instructions or examples provided. The use of Windows tools and PowerShell is prioritized and presented before other SDKs, reinforcing a Windows-first approach.
Recommendations
  • Add Bash/Azure CLI examples for each scenario alongside PowerShell, especially for installation and query execution.
  • Include instructions for using cross-platform tools (e.g., Azure CLI, curl, jq) to demonstrate query acceleration from Linux/macOS environments.
  • Clarify that PowerShell examples can be run on Linux/macOS (if true), or provide alternative Linux-native shell scripts.
  • Avoid using Windows-specific commands (e.g., New-TemporaryFile, Get-Content) without providing Linux equivalents (e.g., mktemp, cat).
  • Reorder or balance the presentation so that Windows and Linux approaches are given equal prominence.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
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 section is less comprehensive and lacks step-by-step guidance. PowerShell is presented before Azure CLI, and Windows-specific tooling (PowerShell) is described in greater detail. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native tools or workflows. The portal instructions are platform-neutral, but the code-based sections favor Windows users.
Recommendations
  • Provide equally detailed Azure CLI examples, including step-by-step breakdowns and sample JSON policy files.
  • Include Bash shell usage examples for Azure CLI commands, demonstrating how Linux users might interact with lifecycle management policies.
  • Add a note clarifying that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider presenting Azure CLI examples before PowerShell to avoid implicit prioritization of Windows tooling.
  • Mention Linux-native automation options (e.g., scripting with Bash, using cron jobs with Azure CLI) where relevant.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides platform-specific examples for monitoring Azure Blob Storage, with a clear ordering that places Windows/PowerShell instructions before cross-platform or Linux-friendly alternatives. PowerShell is presented as a primary scripting interface, and there are no explicit Linux shell (bash) or native Linux tool examples. While Azure CLI is included (which is cross-platform), the absence of explicit Linux shell examples and the prioritization of PowerShell may disadvantage Linux users.
Recommendations
  • Reorder the example tabs so that Azure CLI (which is cross-platform and commonly used on Linux) appears before PowerShell, or at least alternate the order in different sections.
  • Add explicit bash/shell script examples for common monitoring tasks, especially for log analysis and metric retrieval, to demonstrate parity for Linux users.
  • Clarify in the introduction or relevant sections that Azure CLI commands work on all platforms, and provide sample terminal screenshots from both Windows and Linux environments.
  • Where PowerShell-specific cmdlets are shown, consider including equivalent bash/az CLI pipelines or scripts to illustrate Linux workflows.
  • Review referenced screenshots and UI instructions to ensure they do not assume a Windows environment (e.g., file paths, UI conventions).
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. It mentions Windows client support explicitly and provides a workaround using WSL 2, but does not provide direct Linux examples or guidance for mounting NFS shares from native Linux systems. Additionally, enabling static websites is described as possible via PowerShell or Azure CLI, with PowerShell mentioned first, which may imply a Windows-centric approach. There are no explicit Linux commands or tools shown for NFS mounting or management.
Recommendations
  • Add explicit examples for mounting NFS 3.0 shares from native Linux clients, including common mount commands and troubleshooting steps.
  • Mention Linux tools (e.g., mount, showmount) with usage examples, especially where features are unsupported.
  • When listing command-line options (e.g., for enabling static websites), present Azure CLI before PowerShell or provide parity in example order.
  • Clarify that PowerShell is cross-platform, but also provide bash/Linux shell equivalents for all administrative tasks.
  • Include a section on best practices for Linux administrators managing NFS 3.0 on Azure Blob Storage.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides extensive PowerShell examples and instructions, which are primarily relevant to Windows users. PowerShell is featured prominently and in detail, sometimes before Azure CLI examples. File paths in PowerShell examples use Windows-style (C:\temp\json.txt), and there is no mention of Linux shell equivalents (e.g., Bash scripting, Linux file paths). There are no examples using Bash, nor references to Linux-specific tooling or patterns. The documentation assumes familiarity with PowerShell and Windows conventions, which may disadvantage Linux users.
Recommendations
  • Add Bash shell script examples for all Azure CLI workflows, including file operations and JSON manipulation, using Linux-style paths (e.g., /tmp/json.txt).
  • Explicitly mention that Azure CLI commands work cross-platform and provide guidance for Linux/Mac users (e.g., using 'cat' instead of 'Get-Content').
  • Where PowerShell examples are given, provide equivalent Bash or shell script examples, especially for tasks like file conversion, reading/writing JSON, and variable assignment.
  • Avoid using Windows-specific file paths in generic examples; use neutral or platform-agnostic paths, or provide both Windows and Linux versions.
  • Clarify that PowerShell is available on Linux, but also provide native Linux shell alternatives for users who do not use PowerShell.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows First Visual Studio Heavy 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific tools and workflows, such as Visual Studio and .sln solution files, and providing Windows instructions and screenshots before Linux equivalents. The setup and project creation steps are centered around Visual Studio on Windows, with little to no guidance for Linux or cross-platform development environments. While some Linux instructions are present (e.g., setting environment variables), they are secondary and less detailed. There are no examples or recommendations for Linux IDEs or build workflows, and the code snippets assume a Windows-centric development process.
Recommendations
  • Provide equivalent instructions for Linux and macOS, including project setup using CMake or other cross-platform tools.
  • Include screenshots and guidance for popular Linux IDEs (e.g., VS Code, CLion, Qt Creator) and command-line workflows.
  • Present Linux and Windows instructions side-by-side or in tabs, rather than listing Windows first.
  • Avoid assuming Visual Studio as the default; mention alternatives and provide generic C++ build instructions.
  • Ensure all environment variable and tooling instructions are equally detailed for both platforms.
  • Add troubleshooting tips for Linux-specific issues (e.g., library linking, permissions).
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured as a primary automation example alongside Azure CLI, and Windows-centric tools (PowerShell, Az.Storage module) are referenced throughout. PowerShell examples are given equal prominence to Azure CLI, but there are no explicit Linux shell (bash) or scripting examples, nor any mention of Linux-specific patterns or tools. The documentation assumes familiarity with PowerShell and Windows-style scripting, and does not provide parity for Linux users beyond Azure CLI commands.
Recommendations
  • Add explicit bash shell examples for all CLI commands, demonstrating usage in Linux environments (e.g., variable assignment, date handling).
  • Include notes or sections on running Azure CLI commands in Linux/macOS terminals, addressing common differences (e.g., quoting, environment variables).
  • Reference Linux-native tools or scripting patterns where appropriate, such as using cron for scheduling restores or jq for parsing CLI output.
  • Clarify that PowerShell examples are applicable on Linux and macOS (where PowerShell Core is available), or provide alternative bash scripts.
  • Ensure that any prerequisites or installation instructions for CLI tools include Linux-specific guidance (e.g., apt-get/yum for Azure CLI installation).
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-host-keys.md ...orage/blobs/secure-file-transfer-protocol-host-keys.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-specific tools (WinSCP, Windows registry) are mentioned explicitly, and Windows file paths (C:\Users\<user>/.ssh/known_hosts) are used in error messages and instructions. The registry example is Windows-only, and there is no equivalent Linux GUI client example (e.g., FileZilla, Nautilus). The known_hosts example uses a generic Unix path (~/.ssh/known_hosts), but the error and verification instructions repeatedly use Windows paths. No Linux-specific instructions or screenshots are provided for common Linux SFTP clients.
Recommendations
  • Add explicit examples and instructions for Linux SFTP GUI clients (e.g., FileZilla, Nautilus, GNOME Files), including where host keys are stored.
  • When showing file paths, use both Windows and Linux/Unix conventions (e.g., C:\Users\<user>/.ssh/known_hosts and ~/.ssh/known_hosts).
  • Include Linux-specific error messages and troubleshooting steps for host key verification failures.
  • Provide parity for registry key instructions by mentioning Linux equivalents (if any), or clarify that registry is Windows-specific.
  • If mentioning Windows tools first, also mention Linux tools in parallel or before Windows tools in at least some sections.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/secure-file-transfer-protocol-support-authorize-access.md ...secure-file-transfer-protocol-support-authorize-access.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed PowerShell examples for creating and managing SFTP local users and permissions, which are primarily relevant to Windows environments. PowerShell is presented as a first-class option alongside Azure CLI and Portal, but there are no explicit Linux shell (bash) or native Linux tool examples. References to key management and generation do mention ssh-keygen (a Linux/Unix tool), but the step-by-step command-line instructions are focused on PowerShell and Azure CLI, both of which are more commonly used on Windows. There is also a subtle Windows-first bias in the ordering and depth of PowerShell coverage.
Recommendations
  • Add explicit bash/Linux shell examples for all command-line operations, especially for key generation, user creation, and permission assignment.
  • Include references to native Linux tools (e.g., curl, openssh utilities) for interacting with Azure Blob Storage via SFTP.
  • Balance the depth of PowerShell and Azure CLI examples with equivalent Linux-native instructions.
  • Clearly indicate cross-platform compatibility for Azure CLI and provide troubleshooting tips for Linux users.
  • Consider reordering examples so that platform-neutral or Linux-native approaches are presented before or alongside Windows/PowerShell methods.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways. SFTP command examples are presented in PowerShell syntax, and the only explicit SFTP usage example references OpenSSH for Windows Server. There are no Linux-specific examples or mentions of Linux-native tools or workflows, despite SFTP being widely used on Linux. Additionally, references to SSH key management link to instructions for 'SSH from Windows', and the order of presentation favors Windows tools and patterns over Linux equivalents.
Recommendations
  • Provide SFTP command examples using standard Linux shell syntax (e.g., bash), not just PowerShell.
  • Include explicit references and examples for Linux users, such as using OpenSSH on Linux, or common Linux SFTP clients.
  • Balance documentation by mentioning both Windows and Linux workflows/tools when discussing SSH key generation, SFTP usage, and authentication.
  • Link to Linux SSH key management documentation in addition to Windows instructions.
  • Where client lists are given, highlight cross-platform or Linux-native clients, and provide parity in troubleshooting or configuration notes.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured as a primary command-line example before Azure CLI, and there are no explicit Linux shell (bash) or cross-platform scripting examples. The PowerShell section assumes familiarity with Windows tooling, while the Azure CLI section is more platform-neutral but lacks explicit Linux context (e.g., bash usage, Linux package installation). No Linux-specific instructions or screenshots are provided, and the portal instructions are platform-agnostic but do not address Linux desktop nuances.
Recommendations
  • Add explicit bash examples for Azure CLI commands, including Linux-specific installation instructions.
  • Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide platform-specific notes where relevant.
  • Include screenshots or instructions for Linux desktop environments when describing portal usage.
  • Consider adding a section for scripting with bash or other Linux-native tools, or mention cross-platform automation options.
  • Reorder command-line sections to present Azure CLI before PowerShell, as CLI is more platform-neutral.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-auth-abac-examples.md ...n/articles/storage/blobs/storage-auth-abac-examples.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page provides detailed Azure Blob Storage ABAC condition examples, but all command-line examples are exclusively for Azure PowerShell, with no equivalent Bash, Azure CLI, or Linux shell examples. The use of PowerShell and Windows-centric tools is pervasive, and there is no mention of Linux or cross-platform alternatives. This creates a strong Windows bias and leaves Linux users without direct guidance for implementing or testing these scenarios.
Recommendations
  • Add equivalent Azure CLI (az) examples for each PowerShell script, demonstrating how to set and test conditions using Bash or Linux shell environments.
  • Include notes or sections highlighting cross-platform compatibility and how Linux/macOS users can perform the same tasks.
  • Reference or link to documentation for Azure CLI and REST API usage for role assignment conditions.
  • Where file paths or scripting are shown, provide both Windows and Linux path formats.
  • Explicitly state that all examples are applicable to both Windows and Linux, and clarify any platform-specific differences.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by frequently referencing Windows-specific tools (PowerShell) and patterns. PowerShell is presented as a primary automation method, and instructions for Azure CLI suggest using Windows PowerShell as the default terminal, even though Azure CLI is cross-platform. There is little mention of Linux-specific shells or workflows, and examples do not clarify usage on Linux or macOS. The documentation assumes familiarity with Windows environments and tools, which may disadvantage Linux users.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example commands for Bash or other common Linux shells.
  • When referencing command consoles, suggest alternatives such as Bash, Zsh, or Terminal on macOS, not just Windows PowerShell.
  • Balance PowerShell examples with Bash equivalents where possible, or clarify that PowerShell is available cross-platform.
  • Avoid language that implies Windows is the default or preferred environment (e.g., 'open a command console application such as Windows PowerShell').
  • Add notes or sections for Linux/macOS users, including installation and usage tips for Azure CLI and PowerShell on those platforms.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-index-how-to.md ...in/articles/storage/blobs/storage-blob-index-how-to.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by frequently referencing Windows-specific tools (PowerShell) and patterns, and by suggesting Windows PowerShell as the default local shell for Azure CLI usage. Examples use Windows file paths (e.g., C:\demo-file.txt) and mention Windows PowerShell before alternatives. There is little to no mention of Linux shells (e.g., Bash), Linux file paths, or cross-platform considerations in command examples.
Recommendations
  • Explicitly mention that Azure CLI commands can be run in Bash or other Linux shells, not just Windows PowerShell.
  • Provide Linux/macOS file path examples (e.g., /home/user/demo-file.txt) alongside Windows paths.
  • Use neutral language when referring to local shells, such as 'open a command console (e.g., PowerShell, Bash, Terminal)'.
  • Add notes or tabs for Linux/macOS usage where relevant, especially for command-line examples.
  • Ensure that instructions for installing and running tools (like Azure CLI) include Linux/macOS steps and references.
  • Avoid implying that PowerShell is the default or preferred shell for Azure CLI unless specifically required.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways: PowerShell is presented as a primary method for enabling the change feed, with detailed step-by-step instructions, while Linux-specific methods (such as Bash scripting or cross-platform CLI usage) are not covered. The Azure portal and PowerShell are mentioned before Azure CLI, and no Linux shell examples or explicit Linux tooling are provided. There is no mention of Linux-specific considerations, nor are there examples using Bash, zsh, or other Linux-native tools.
Recommendations
  • Add explicit Bash or shell script examples for enabling and managing the change feed using Azure CLI, demonstrating usage on Linux or macOS.
  • Present Azure CLI examples before PowerShell, or at least in parallel, to avoid Windows-first ordering.
  • Include notes or sections on Linux/macOS compatibility, such as installing Azure CLI on Linux, and using it from a Linux terminal.
  • Provide parity in troubleshooting and operational guidance for Linux users, including references to Linux-native tools (e.g., azcopy, jq for JSON processing, etc.).
  • Avoid assuming PowerShell as the default scripting environment; clarify that Azure CLI works cross-platform and show equivalent commands for Linux and macOS.
  • Consider adding a table comparing methods for Windows, Linux, and macOS, to make it clear that all platforms are supported equally.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-inventory-report-analytics.md ...orage/blobs/storage-blob-inventory-report-analytics.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references Power BI Desktop, a Windows-only tool, for data visualization, and does not mention or provide alternatives for Linux users. There are no examples or instructions for running the visualization step on Linux or using cross-platform tools. The installation guidance for Power BI is Windows-centric, and no Linux-compatible visualization options (such as Power BI web, Jupyter, or open-source BI tools) are suggested. The order of presentation assumes Windows as the default environment.
Recommendations
  • Include instructions for using Power BI web (which is browser-based and cross-platform) to visualize reports.
  • Suggest and provide examples for open-source, cross-platform BI tools (e.g., Apache Superset, Grafana, Tableau Public) for Linux users.
  • Add explicit notes or sections for Linux and macOS users, including installation and usage guidance for visualization steps.
  • Present visualization tool options in a platform-neutral order, or explicitly mention alternatives before or alongside Windows-only tools.
  • Where screenshots or step-by-step instructions are given, clarify which are Windows-specific and provide Linux/macOS equivalents if possible.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-static-website-how-to.md ...es/storage/blobs/storage-blob-static-website-how-to.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by frequently referencing Windows tools (PowerShell), providing Windows-centric instructions (e.g., opening Windows PowerShell), and using Windows file paths in examples. PowerShell is given its own section, and instructions often mention Windows before Linux or cross-platform alternatives. There are no explicit Linux shell examples (e.g., Bash), and references to local CLI usage default to Windows environments. Linux-specific instructions, file paths, or troubleshooting are missing.
Recommendations
  • Include explicit Bash shell examples alongside PowerShell, especially for Azure CLI usage.
  • Use cross-platform file path examples (e.g., /home/user/site) in addition to Windows paths (e.g., C:\temp\index.html).
  • Clarify that Azure CLI and AzCopy are cross-platform and provide installation/use instructions for Linux and macOS.
  • Avoid phrases like 'open a Windows PowerShell command window'; instead, use 'open a terminal or command prompt'.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, path formats).
  • Ensure parity in step-by-step instructions for Linux/macOS users, including screenshots or terminal commands where appropriate.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-static-website.md .../articles/storage/blobs/storage-blob-static-website.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation lists several upload tools, including Azure CLI, Azure PowerShell, AzCopy, Storage Explorer, Azure portal, Azure Pipelines, and VS Code extension. While Azure CLI and AzCopy are cross-platform, the explicit mention of 'Azure PowerShell module' and the ordering (CLI, then PowerShell) suggests a Windows-first approach. There are no explicit Linux-specific examples, nor is there mention of Linux-native tools or shell scripting. The documentation does not provide parity in examples for Linux users, and PowerShell is highlighted as a primary method, which is more common on Windows.
Recommendations
  • Add explicit Linux shell/Bash examples for uploading files (e.g., using Azure CLI in Bash, AzCopy in Linux terminal).
  • Clarify cross-platform support for each tool, especially for AzCopy and Azure CLI.
  • Provide step-by-step instructions or code snippets for Linux users, such as using Bash scripts or integrating with Linux CI/CD tools.
  • Avoid listing PowerShell before CLI or at least alternate the order to avoid Windows-first perception.
  • Mention Linux desktop tools (e.g., Nautilus integration, if available) or note that Storage Explorer is cross-platform.
  • Include a note or section on using these tools from Linux/macOS environments.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-custom-domain-name.md ...n/articles/storage/blobs/storage-custom-domain-name.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 featured prominently as a command-line option, and in several places, PowerShell commands are presented before Azure CLI commands. The phrase 'Run the following PowerShell command' is used even in the Azure CLI sections, which may confuse Linux users. There is no mention of Bash, Linux shell, or cross-platform scripting, and no explicit Linux-specific guidance or examples are provided. The Azure Portal instructions are platform-neutral, but the command-line examples and terminology lean toward Windows tools and patterns.
Recommendations
  • Replace 'Run the following PowerShell command' in Azure CLI sections with 'Run the following Azure CLI command' to avoid confusion.
  • Add explicit notes that both Azure CLI and PowerShell are cross-platform and can be used on Linux, macOS, and Windows.
  • Include Bash shell examples or instructions for Linux users, especially for command-line operations.
  • Clarify that Azure CLI commands can be run in Bash, zsh, or other Linux shells, and provide example command syntax for those environments.
  • Ensure that command-line examples are presented in a platform-neutral order (e.g., Azure CLI before PowerShell, or side-by-side).
  • Add troubleshooting notes or links for Linux users regarding installation and usage of Azure CLI and PowerShell.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-java.md ...rticles/storage/blobs/storage-quickstart-blobs-java.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates some Windows bias, notably by listing PowerShell as the first example in command-line instructions, providing explicit PowerShell and Windows CMD environment variable instructions before Linux equivalents, and referencing Windows-specific tools and output paths (e.g., C:\QuickStarts\blob-quickstart). While Bash examples are present and Linux instructions are included, Windows tools and patterns are often mentioned first or with more detail, and PowerShell is given equal or greater prominence than Bash in several places.
Recommendations
  • Alternate the order of command-line examples, sometimes listing Bash/Linux first to avoid reinforcing Windows-first patterns.
  • Provide equal detail and context for Linux/Bash instructions, including example output paths and troubleshooting notes relevant to Linux environments.
  • Where possible, use platform-neutral language and avoid referencing Windows-specific paths (e.g., C:\...) in generic output examples.
  • Ensure that all instructions for environment variables, authentication, and directory navigation are equally clear for Linux users.
  • Consider adding explicit notes or tips for Linux/macOS users where Windows-specific behavior or tools are discussed.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a noticeable Windows bias. Windows tools (Visual Studio, PowerShell, CMD) are mentioned first or exclusively in several sections. PowerShell is given as a primary example for package installation and role assignment, and Visual Studio is the only IDE explicitly required in prerequisites. Linux equivalents (Bash, Azure CLI, VS Code) are mentioned, but often after Windows tools or with less detail. Some steps (like setting environment variables) provide both Windows and Linux commands, but the overall flow and examples favor Windows environments.
Recommendations
  • Add Linux-first or parity examples for all command-line instructions, including role assignment and package installation.
  • Include Linux-native IDEs (such as VS Code) in prerequisites, not just Visual Studio.
  • Provide Bash and Azure CLI examples before or alongside PowerShell and CMD examples.
  • Clarify that the tutorial is cross-platform and highlight any platform-specific differences.
  • Ensure that all tooling and workflow steps have equivalent instructions for Linux/macOS users.
  • Consider adding a section or tab for macOS where relevant.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-dotnet.md ...icles/storage/blobs/storage-quickstart-blobs-dotnet.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Visual Studio Heavy Powershell Mention Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Visual Studio (Windows-only) is presented as the first and primary IDE option, with detailed step-by-step instructions and screenshots. The .NET CLI instructions mention 'cmd, PowerShell, or Bash' but do not provide any Linux-specific guidance or screenshots. There is no mention of Linux-native editors (other than a brief reference to VS Code), nor are there examples of Linux-specific commands, file paths, or troubleshooting steps. The package installation and project setup instructions are Windows-centric, and the clean-up section references Azure CLI but does not show Linux shell usage or alternatives.
Recommendations
  • Provide equal prominence and detail for Linux development environments, such as step-by-step instructions for using the .NET CLI on Linux, including screenshots of Linux terminals.
  • Include explicit Linux shell commands and file path examples (e.g., using $HOME/data instead of ./data where appropriate).
  • Add troubleshooting steps relevant to Linux users (e.g., permissions, case sensitivity, package manager issues).
  • Mention and show usage of Linux-native editors (e.g., Vim, Nano, Emacs) alongside Visual Studio and VS Code.
  • Ensure that all references to command-line tools (such as Azure CLI) include Linux installation and usage notes.
  • Avoid presenting Windows tools or workflows first; use parallel tabbed instructions for Windows and Linux where possible.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-nodejs-typescript.md ...ge/blobs/storage-quickstart-blobs-nodejs-typescript.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation exhibits a mild Windows bias. Windows tools and workflows (cmd, PowerShell, Visual Studio Code) are mentioned first or exclusively in several places, especially in instructions for opening the project, authenticating, and setting environment variables. PowerShell is given a dedicated authentication section, and Visual Studio Code is emphasized as the editor, which is more common on Windows. Linux instructions are present but often appear after Windows ones or are less detailed.
Recommendations
  • Present instructions for Windows, Linux, and macOS in parallel tabbed sections wherever possible, rather than listing Windows first.
  • Include Linux/macOS equivalents for all command-line and tool-based steps (e.g., suggest nano/vim for editing files, or mention alternative editors).
  • For authentication, give equal prominence to Azure CLI (cross-platform) and PowerShell, and clarify which are available on which platforms.
  • When referencing opening a terminal or console, use neutral language (e.g., 'terminal' instead of 'cmd, PowerShell, or Bash'), or list Bash first for parity.
  • Where Visual Studio Code is recommended, also mention that any editor can be used, and provide instructions for opening the project in a generic way.
  • Ensure all environment variable instructions are provided for Windows, Linux, and macOS, and consider using tabbed formatting for clarity.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-static-website-terraform.md ...e/blobs/storage-quickstart-static-website-terraform.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell example is given equal prominence and is presented immediately after the CLI example. There are no explicit Linux shell (bash/sh) examples, nor is there mention of Linux-specific tools or workflows. The use of PowerShell may implicitly favor Windows users, and the lack of explicit Linux shell commands or instructions may make the documentation less accessible to Linux users.
Recommendations
  • Add explicit bash/sh examples for Linux users, especially for command-line steps such as retrieving outputs and opening URLs.
  • Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any necessary platform-specific notes.
  • If PowerShell is included, consider also including bash equivalents, or at least indicate which commands are cross-platform.
  • Review the order of examples to avoid implicit prioritization of Windows tools; consider listing CLI/bash examples first or side-by-side.
  • Mention installation and usage steps for Linux environments where relevant, such as for Terraform and Azure CLI.
GitHub Create Pull Request
← Previous Page 18 of 67 Next →