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 601-625 of 1657 flagged pages
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias. In several places, Windows-centric tools (PowerShell) are mentioned before cross-platform alternatives (Azure CLI), and instructions reference Windows PowerShell as the default console application. The PowerShell examples are detailed and prominent, and there is an assumption that users are familiar with Windows tooling. There are no explicit Linux shell examples (e.g., bash), nor is there guidance for Linux-specific environments or shell usage. The Azure CLI instructions do not clarify Linux usage, and the mention of 'Windows PowerShell' as the console application for CLI is misleading for Linux users.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, including using bash/zsh terminals.
  • When referencing Azure CLI, clarify that it runs on Windows, Linux, and macOS, and provide example commands in bash syntax (e.g., export variables, use $HOME).
  • Avoid referring to 'Windows PowerShell' as the default console for CLI; instead, use 'command-line terminal' or mention alternatives.
  • Present cross-platform tools (Azure CLI, ARM templates) before or alongside Windows-specific tools (PowerShell) to avoid Windows-first ordering.
  • Include notes or callouts for Linux users regarding authentication, environment setup, and command syntax differences.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/immutable-container-level-worm-policies.md ...orage/blobs/immutable-container-level-worm-policies.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell commands (Remove-AzRmStorageContainer, Remove-AzStorageContainer) before mentioning Azure CLI equivalents. The PowerShell examples are described first, and Windows-centric tooling is highlighted. There are no Linux shell or Bash examples, nor is there mention of Linux-specific patterns or tools. The documentation assumes familiarity with Windows/PowerShell environments and does not provide parity for Linux users.
Recommendations
  • Provide Bash and Linux shell examples for all command-line operations, especially for container deletion and policy management.
  • List Azure CLI commands before or alongside PowerShell commands to avoid Windows-first ordering.
  • Explicitly mention that all operations can be performed from Linux, macOS, and Windows environments, and clarify any platform-specific differences.
  • Include sample scripts or command snippets for Linux users, such as using az CLI in Bash.
  • Avoid exclusive references to Windows tools; ensure documentation is cross-platform by default.
GitHub Create Pull Request
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-08 00:53
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. It references PowerShell commands (Remove-AzRmStorageContainer, Remove-AzStorageContainer) as primary examples for control and data plane operations, and mentions them before the Azure CLI equivalents. The use of PowerShell as a canonical example and the explicit mention of Windows-centric tooling suggests a preference for Windows environments. There are no Linux-specific examples (e.g., Bash, shell scripting), nor is there mention of Linux-native tools or patterns.
Recommendations
  • Provide Linux/Bash shell examples alongside PowerShell commands, especially for common operations like container deletion.
  • When listing command-line tools, present Azure CLI and REST API examples before or alongside PowerShell, as Azure CLI is cross-platform.
  • Explicitly state that all operations can be performed from Linux, macOS, and Windows, and clarify any platform-specific caveats.
  • Include links or references to Linux-specific documentation or tutorials for Azure Storage management.
  • Avoid presenting Windows tools (PowerShell) as the default or primary method unless there is a technical reason.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for enabling and managing container soft delete using the Azure portal, PowerShell, Azure CLI, and ARM templates. However, the PowerShell section is given before the Azure CLI section, and all command-line examples are either PowerShell (Windows-centric) or Azure CLI (cross-platform, but no explicit Linux shell examples). There are no Linux-specific shell (bash) examples, nor are Linux-native tools or patterns mentioned. The documentation implicitly prioritizes Windows tools and workflows by listing PowerShell before CLI and omitting Linux-specific guidance.
Recommendations
  • Add explicit bash examples for Azure CLI commands, demonstrating usage in Linux/macOS terminals.
  • Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider listing Azure CLI before PowerShell to reflect its cross-platform nature and reduce perceived Windows-first bias.
  • If relevant, include instructions for using REST API or SDKs from Linux environments.
  • Clarify that PowerShell Core is available on Linux/macOS, if PowerShell is to be included, and provide installation guidance for those platforms.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides example workflows for Azure portal, PowerShell, and Azure CLI. PowerShell is featured prominently and often appears before Azure CLI, which is more cross-platform. There are no Linux-specific shell examples (e.g., Bash), and the use of PowerShell commands and terminology may be more familiar to Windows users. The documentation does not mention Linux tools or patterns, nor does it provide guidance for Linux environments beyond the Azure CLI, which is platform-agnostic but not highlighted as such.
Recommendations
  • Add explicit Bash shell examples for Linux users alongside PowerShell, especially for scripting common operations.
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
  • Where PowerShell is mentioned, note that PowerShell Core is available on Linux and macOS, and provide installation instructions or links.
  • Avoid presenting PowerShell before Azure CLI to reduce perceived Windows-first bias; alternate or randomize the order, or lead with CLI.
  • Include troubleshooting or environment setup notes for Linux users, such as package managers or shell differences.
  • Reference Linux-native tools or patterns where appropriate, and ensure terminology is inclusive of non-Windows environments.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Visual Studio 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 files, and by providing setup instructions and screenshots exclusively for Windows. Linux equivalents for project setup (e.g., using CMake directly, or other IDEs) are not mentioned, and the initial instructions assume a Windows development environment. While environment variable setup is shown for both Windows and Linux, the overall flow and examples are Windows-centric.
Recommendations
  • Add explicit instructions for setting up a C++ project on Linux, such as using CMake or other cross-platform build systems.
  • Include screenshots or examples for popular Linux IDEs (e.g., VS Code, CLion) or command-line workflows.
  • Provide guidance for opening and editing source files on Linux (e.g., using editors like vim, nano, or VS Code), rather than only referencing Visual Studio and .sln files.
  • Ensure all code snippets and setup steps are clearly marked as cross-platform, and highlight any platform-specific differences.
  • Consider reordering instructions so that cross-platform or Linux steps are presented alongside or before Windows-specific steps.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page consistently provides Azure PowerShell examples for all role assignment condition scenarios, but does not include equivalent examples for Linux shells (such as Bash, CLI, or scripting with az CLI). The only command-line tooling referenced is Azure PowerShell, which is most commonly used on Windows. There are no Linux-specific instructions, nor are cross-platform alternatives (like Azure CLI) mentioned. This creates a strong Windows bias, both in tooling and in example coverage.
Recommendations
  • Add equivalent Azure CLI (az) examples for each PowerShell sample, showing how to set conditions and test them using Bash or other Linux shells.
  • Explicitly mention that all examples can be run on Linux, macOS, and Windows, and provide platform-agnostic instructions where possible.
  • Include sample scripts for Bash and/or cross-platform scripting languages (e.g., Python with Azure SDK) alongside PowerShell.
  • Reference installation and usage of Azure CLI as an alternative to PowerShell, especially for users on Linux or macOS.
  • Where screenshots or instructions reference Windows-specific tools or UI, add notes or visuals for Linux/macOS equivalents if available.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific tools (WinSCP, registry keys) are mentioned and exemplified before Linux equivalents, and the only explicit client tool example is WinSCP (Windows). The registry key example is Windows-only, while the 'known_hosts' example is generic but lacks explicit Linux client references (e.g., OpenSSH, FileZilla, etc.). There is no explicit Linux or macOS GUI client example, and the troubleshooting output uses a Windows file path (C:\Users\<user>/.ssh/known_hosts), which is not standard for Linux/macOS.
Recommendations
  • Add explicit Linux/macOS client examples (e.g., OpenSSH, FileZilla, Nautilus, Cyberduck) and their trusted host storage locations.
  • Provide troubleshooting output using Linux/macOS file paths (e.g., /home/<user>/.ssh/known_hosts or ~/.ssh/known_hosts) alongside Windows paths.
  • Include Linux-specific instructions for managing known_hosts (e.g., using ssh-keygen -R, editing ~/.ssh/known_hosts).
  • Mention Linux GUI SFTP clients and how they handle host keys.
  • Balance the order of presentation so that Windows and Linux tools/examples are given equal prominence.
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-08 00:53
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 PowerShell as the default local shell for Azure CLI usage, providing file path examples in Windows format (e.g., C:\demo-file.txt), and prioritizing PowerShell examples. There is little to no mention of Linux shells (bash, zsh) or Linux file path conventions, and Windows tools (PowerShell) are referenced before their Linux equivalents. This may make the documentation less approachable for Linux/macOS users.
Recommendations
  • When referencing local shell usage for Azure CLI, mention both Windows PowerShell and common Linux/macOS shells (e.g., bash, zsh).
  • Provide file path examples in both Windows (C:\demo-file.txt) and Linux/macOS (/home/user/demo-file.txt) formats.
  • Avoid using Windows-only terminology (e.g., 'open a command console application such as Windows PowerShell') and instead use neutral language like 'open a terminal or command prompt'.
  • Ensure that CLI and AzCopy examples are explicitly shown to work on Linux/macOS, and note any platform-specific differences.
  • Consider including screenshots or instructions for Linux/macOS environments where relevant.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias in several ways: PowerShell is featured as a primary method for enabling the change feed, with detailed step-by-step instructions and module installation guidance. Windows-centric tools (PowerShell, Azure Portal) are mentioned before or instead of Linux alternatives. There are no Linux shell (bash) or cross-platform scripting examples for enabling the change feed, nor is there mention of Linux-specific tools or patterns. The CLI example is present, but the PowerShell section is more extensive and detailed, and there is no parity for Linux users in terms of guidance or troubleshooting.
Recommendations
  • Add bash shell examples for enabling/disabling change feed using Azure CLI, including authentication and troubleshooting steps relevant to Linux environments.
  • Include references to cross-platform tools such as Azure Storage Explorer and clarify their availability on Linux and macOS.
  • Balance the detail level between PowerShell and CLI sections, ensuring Linux users receive equally comprehensive instructions.
  • Explicitly mention that Azure CLI is cross-platform and provide installation instructions for Linux/macOS.
  • Where PowerShell modules are discussed, offer equivalent bash/CLI scripts for Linux users.
  • Review the order of presentation so that cross-platform or CLI methods are listed before Windows/PowerShell-specific instructions.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias by presenting the only explicit connection example as a Windows PowerShell session, referencing Windows-specific OpenSSH documentation, and omitting equivalent Linux/macOS command-line examples. The initial example and guidance are tailored for Windows users, with no mention of Linux or cross-platform usage patterns until generic SFTP client documentation is referenced.
Recommendations
  • Add explicit Linux/macOS command-line examples for connecting to Azure Blob Storage via SFTP (e.g., using 'sftp' from a Bash shell).
  • Reference both Windows and Linux OpenSSH documentation, or provide links to cross-platform OpenSSH usage guides.
  • Present connection examples for multiple platforms side-by-side, or clarify that the commands are applicable across platforms.
  • Avoid using Windows-specific prompts (e.g., 'PS C:\Users\temp>') as the sole example; include '$' or other platform-neutral prompts.
  • Mention popular Linux SFTP clients (e.g., FileZilla, command-line sftp) and provide usage notes if there are platform-specific considerations.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation lists Windows-centric tools (Azure PowerShell, Visual Studio Code extension, Azure Storage Explorer) prominently and includes PowerShell as a primary example for uploading content. While Azure CLI and AzCopy are cross-platform, the inclusion and ordering of Windows-specific tools and patterns (PowerShell, VS Code extension, Storage Explorer) before mentioning Linux-native equivalents or workflows suggests a Windows-first bias. There are no explicit Linux shell examples (e.g., Bash), nor are Linux-specific tools or workflows highlighted.
Recommendations
  • Add explicit Linux/Bash examples for common tasks, such as uploading files using Azure CLI or AzCopy from a Linux shell.
  • Reorder tool lists to start with cross-platform tools (Azure CLI, AzCopy) before Windows-specific ones (PowerShell, Storage Explorer).
  • Include guidance or screenshots for Linux users (e.g., terminal usage, file paths) alongside Windows/PowerShell instructions.
  • Mention Linux-native editors (e.g., Vim, nano) or workflows for preparing and uploading website files.
  • Clarify which tools are cross-platform and provide links to installation instructions for Linux.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias in several ways: Windows tools (PowerShell) are featured prominently and often referenced before or instead of Linux alternatives; instructions frequently mention opening 'Windows PowerShell' and use Windows-style paths (e.g., C:\temp\index.html) without providing equivalent Linux shell or path examples. There is also a lack of explicit Linux/Bash examples, especially in sections discussing local CLI usage and file paths, and no mention of Linux-specific considerations for PowerShell or AzCopy usage.
Recommendations
  • Provide explicit Bash/Linux shell examples alongside PowerShell, especially for CLI commands and file uploads.
  • Mention Linux/Mac equivalents for file paths (e.g., /home/user/index.html) wherever Windows paths are shown.
  • Clarify that Azure CLI commands work cross-platform and show how to run them in Bash or other Linux shells.
  • For PowerShell instructions, note that PowerShell Core is available on Linux and Mac, and provide guidance for those platforms.
  • When referencing tools like AzCopy, include installation and usage instructions for Linux/Mac as well as Windows.
  • Avoid phrases like 'Open a Windows PowerShell command window'—use 'Open a terminal or PowerShell window' and specify platform differences as needed.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing Power BI Desktop (a Windows-only tool) for data visualization, without mentioning Linux-compatible alternatives or providing instructions for Linux users. There are no examples or guidance for running equivalent workflows on Linux, such as using Power BI on the web, alternative visualization tools, or command-line approaches. The instructions for downloading and opening files assume a Windows file dialog and user experience. No Linux-specific tools, patterns, or examples are provided.
Recommendations
  • Include instructions for using Power BI Service (web-based) for users on Linux and macOS.
  • Mention and provide examples for alternative visualization tools that are cross-platform, such as Tableau Public, Apache Superset, or Jupyter Notebooks with visualization libraries (matplotlib, seaborn, plotly).
  • Clarify that Power BI Desktop is only available on Windows and suggest alternatives for other operating systems.
  • Provide command-line or browser-based workflow options for file downloads and uploads, suitable for Linux environments.
  • Add screenshots and step-by-step guidance for Linux users where applicable, especially for tasks like file manipulation and visualization.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates some Windows bias, particularly in the order and emphasis of tooling and instructions. Windows tools (cmd, PowerShell, Visual Studio Code) are mentioned first or exclusively in several places, and PowerShell is given its own authentication section. Linux equivalents are present but often appear after Windows instructions or are less detailed.
Recommendations
  • When listing console options, use neutral or alphabetical order (e.g., 'Bash, cmd, or PowerShell') rather than putting Windows tools first.
  • For authentication instructions, provide equal prominence and detail for Linux/macOS tools (e.g., Bash, Azure CLI) as for Windows tools like PowerShell.
  • Where Visual Studio Code is referenced, clarify that it is cross-platform and provide alternative editors for Linux users if relevant.
  • In environment variable setup, present Linux/macOS and Windows instructions side-by-side or in parallel tabs, rather than listing Windows first.
  • Audit all code snippets and instructions to ensure Linux users are not required to infer steps from Windows-centric examples.
  • Consider adding explicit notes or sections for Linux/macOS users where workflows or tooling differ.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows tools and workflows (Visual Studio, PowerShell, setx for environment variables) are mentioned first or exclusively in several places. PowerShell is given as a primary example for package installation and role assignment, and Visual Studio is the only full-featured IDE mentioned. While Linux alternatives (Azure CLI, Bash, Visual Studio Code) are present, they are often listed after Windows options or with less detail. Some steps, such as setting environment variables, provide Windows-specific instructions first and more context, while Linux instructions are brief. There are no examples for MacOS, and the overall workflow assumes a Windows-centric development environment.
Recommendations
  • Ensure Linux and macOS examples are presented with equal prominence and detail as Windows examples.
  • List cross-platform tools (e.g., Azure CLI, VS Code) before platform-specific ones (PowerShell, Visual Studio) where possible.
  • Provide explicit macOS instructions for environment variable setup and other platform-specific steps.
  • Include Linux-first or cross-platform-first code blocks and workflows, especially for common developer tasks.
  • Mention alternative editors (e.g., JetBrains Rider) and terminal environments for non-Windows users.
  • Clarify when steps are identical across platforms to avoid unnecessary Windows-centric framing.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-python.md ...icles/storage/blobs/storage-quickstart-blobs-python.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias. Examples and instructions for signing in to Azure are given for Azure CLI, Visual Studio Code, and PowerShell, with PowerShell called out as a distinct tab. When setting environment variables for the connection string, Windows instructions (using 'setx') are presented before Linux instructions (using 'export'). The mention of 'console window (such as PowerShell or Bash)' puts PowerShell first, and Windows-specific tools and patterns (PowerShell, setx) are included throughout. There are no Linux-exclusive examples, and Linux instructions are present but secondary.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which comes first to avoid implicit prioritization.
  • When listing console options, use neutral phrasing (e.g., 'such as Bash or PowerShell') or list Bash first.
  • Provide explicit Bash and Linux terminal examples where PowerShell is shown, and consider including macOS instructions if relevant.
  • Ensure that environment variable instructions for Linux are given equal prominence and detail as Windows.
  • Add notes or tabs for Linux-specific authentication flows (e.g., using Azure CLI in Bash) and clarify any OS-specific differences.
  • Review code snippets and instructions to ensure they are cross-platform and do not assume Windows as the default environment.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/versioning-enable.md .../blob/main/articles/storage/blobs/versioning-enable.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. PowerShell is featured prominently as a primary scripting example, and is presented before Azure CLI in all relevant sections. There is a lack of explicit Linux shell (bash) examples, and no mention of Linux-specific tools or patterns. The use of PowerShell and Windows-centric terminology (e.g., PowerShell module installation) may disadvantage Linux users, even though Azure CLI is cross-platform.
Recommendations
  • Add explicit bash examples for Azure CLI commands, including variable setting and command usage in a Linux shell context.
  • Ensure that Azure CLI examples use syntax and variable conventions familiar to Linux users (e.g., export, $VAR, single quotes).
  • Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform and more widely used on Linux.
  • Mention that Azure CLI works on Linux, macOS, and Windows, and provide installation instructions for Linux.
  • Avoid assuming PowerShell as the default scripting environment; clarify that PowerShell examples are for Windows users.
  • Where possible, include notes or links to Linux-specific guidance for Azure Storage management.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/classic-account-migration-process.md ...es/storage/common/classic-account-migration-process.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently mentioning PowerShell and the Azure portal (which is most commonly used on Windows) as primary migration tools, listing PowerShell before Azure CLI in references, and providing links to PowerShell-based migration guides before Linux-friendly alternatives. There are no explicit Linux-specific examples or references to Linux-native tools or shell environments, and the documentation does not address Linux-specific considerations or parity in migration workflows.
Recommendations
  • Ensure that Azure CLI examples and references are given equal prominence to PowerShell, including listing them first or side-by-side where appropriate.
  • Add explicit Linux shell (bash) examples for migration commands and workflows.
  • Reference Linux-native tools and environments (e.g., Bash, Azure CLI on Linux) in the main migration steps and guidance.
  • Include a section or note addressing Linux-specific considerations, such as command syntax differences, authentication methods, or environment setup.
  • Review and update all linked migration guides to ensure Linux parity in examples and instructions.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/authorization-resource-provider.md ...cles/storage/common/authorization-resource-provider.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary tool for assigning Azure roles, mentioning it before Linux-friendly alternatives. The Azure classic CLI is referenced, but there is no mention of the modern cross-platform Azure CLI, nor are there explicit Linux shell or Bash examples. The absence of Linux-specific instructions or parity in tool recommendations may hinder Linux users.
Recommendations
  • Add explicit instructions and examples using the Azure CLI (az), which is cross-platform and widely used on Linux.
  • Include Bash or shell script examples for common management tasks alongside PowerShell examples.
  • Mention Linux and macOS compatibility for all command-line tools, and clarify which tools are available on each platform.
  • Reorder tool recommendations to list cross-platform tools (Azure CLI, REST API) before platform-specific ones (PowerShell).
  • Provide links to installation guides for Azure CLI on Linux and macOS.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/classic-account-migration-overview.md ...s/storage/common/classic-account-migration-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows evidence of Windows bias, particularly in its references to PowerShell cmdlets for managing Azure storage accounts. The FAQ section discusses the use of legacy and modern PowerShell cmdlets for account management, without mentioning Linux-native tools or cross-platform alternatives (such as Azure CLI or REST API usage). There is no mention of Linux shell commands, nor are Linux-specific migration patterns or tools referenced. The documentation also refers to the Azure Portal, which is cross-platform, but the command-line examples and tool recommendations are Windows-centric.
Recommendations
  • Add examples using Azure CLI (az storage ...) for all migration and management operations, as Azure CLI is cross-platform and widely used on Linux.
  • Reference REST API usage for migration and management tasks, providing sample requests and responses.
  • Explicitly mention that all operations can be performed from Linux, macOS, and Windows, and provide parity in command-line instructions.
  • Include links to documentation for Azure CLI and REST API equivalents wherever PowerShell cmdlets are mentioned.
  • Avoid language that implies PowerShell is the primary or only supported method for automation; present CLI and API options first or alongside PowerShell.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias in several ways: PowerShell is presented as a primary command-line option alongside the Azure Portal, with Azure CLI examples following PowerShell and even incorrectly labeled as 'PowerShell command' in the CLI section. There is a strong emphasis on PowerShell usage, which is native to Windows, and no mention of Linux-specific shell environments or patterns. The ordering of examples consistently places Windows-centric tools (Portal, PowerShell) before cross-platform alternatives (Azure CLI).
Recommendations
  • Correct the labeling in the Azure CLI sections to remove references to PowerShell, ensuring clarity for Linux/macOS users.
  • Explicitly mention that Azure CLI commands can be run in Bash, Zsh, or other Linux/macOS shells, and provide example shell environments.
  • Where PowerShell is referenced, consider providing equivalent Bash commands for common tasks (e.g., string manipulation, file copying) if relevant.
  • Add notes or sections for Linux/macOS users, such as how to install and use Azure CLI on those platforms.
  • Consider alternating the order of examples (e.g., present Azure CLI before PowerShell in some sections) to avoid reinforcing a Windows-first perspective.
  • Review and update any terminology that assumes a Windows environment (e.g., 'PowerShell command' for CLI examples) to be platform-neutral.
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-08 00:53
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 does not include explicit Linux shell (bash/sh) examples. PowerShell, which is primarily a Windows tool, is given equal prominence to Azure CLI, and there is no mention of Linux-specific patterns or tools. The ordering of tabs puts Azure CLI first, but the lack of a dedicated Linux shell example and the inclusion of PowerShell may suggest a slight Windows bias.
Recommendations
  • Add explicit bash/sh examples for Linux users, especially for command-line steps.
  • Clarify that Azure CLI commands work cross-platform and provide any necessary Linux-specific notes (e.g., environment variable syntax differences).
  • Consider including screenshots or instructions for Linux terminals where applicable.
  • If PowerShell is included, note its availability on Linux, or clarify when Windows-only features are used.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows (PowerShell, CMD) and Linux (Bash) examples for most commands, but Windows-specific tools and instructions (PowerShell, setx, Connect-AzAccount) are often listed first or given prominence. There is a slight bias toward Windows environments, with Windows instructions and screenshots appearing before or in more detail than Linux equivalents. Some output examples use Windows-style paths (e.g., C:\QuickStarts\blob-quickstart), and authentication instructions include PowerShell tabs and commands. However, Linux parity is generally present, and Bash examples are included throughout.
Recommendations
  • Alternate the order of Windows and Linux instructions/tabs to avoid always listing Windows first.
  • Ensure Linux/Bash instructions are as detailed and prominent as Windows/PowerShell instructions.
  • Include Linux-style output examples (e.g., /home/user/QuickStarts/blob-quickstart) alongside Windows-style ones.
  • Where screenshots show Windows interfaces, consider also including Linux equivalents or clarifying cross-platform applicability.
  • When referencing authentication tools, mention Bash/Azure CLI first or equally with PowerShell.
  • Review all sections for subtle language or ordering that prioritizes Windows, and adjust for parity.
GitHub Create Pull Request
Storage https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/customer-managed-keys-configure-cross-tenant-new-account.md ...stomer-managed-keys-configure-cross-tenant-new-account.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for configuring cross-tenant customer-managed keys for a new Azure Storage account using the Azure portal, PowerShell, and Azure CLI. The PowerShell example is prominent and detailed, which may indicate a bias toward Windows environments. There is no mention of Linux-specific tools, shell environments, or scripting patterns, and the CLI example does not clarify cross-platform usage (e.g., Bash vs. CMD). No Linux-specific guidance or troubleshooting is provided, and PowerShell is presented before CLI, which is more commonly used in Linux environments.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, including environment setup and variable usage.
  • Clarify that Azure CLI commands work cross-platform and provide notes or troubleshooting for Linux users (e.g., permissions, path differences).
  • Include references to Linux-native tools or scripting patterns where applicable.
  • Consider presenting Azure CLI examples before PowerShell to better serve Linux and cross-platform users.
  • Add a note or section on using PowerShell Core on Linux, if PowerShell examples are retained.
GitHub Create Pull Request
← Previous Page 25 of 67 Next →