Document Details
Blob Cli
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides Bash-based Azure CLI examples, which are generally cross-platform, but consistently uses Windows-style file paths (e.g., C:\temp\) and references to Windows filesystem locations in variable assignments and instructions. There are no explicit Linux or macOS path examples, and the XML file example instructs users to create files in C:\temp, a Windows-specific directory. This may confuse or exclude Linux/macOS users, as no equivalent Linux paths (e.g., /tmp or ~/temp) are shown. No PowerShell-specific commands or Windows-only tools are used, but the path conventions and file location instructions display a subtle Windows-first bias.
Recommendations
- Provide both Windows and Linux/macOS path examples in all code snippets and instructions (e.g., use $HOME/temp or /tmp for Linux/macOS, and C:\temp for Windows).
- Add a note at the start of the article clarifying that file paths should be adapted to the user's OS, with examples for each.
- When referencing file creation or locations (such as the XML file example), include both Windows and Linux/macOS instructions.
- Consider using environment variables (like $HOME or %USERPROFILE%) in examples to make them more cross-platform.
- Explicitly state that the Bash examples work on both Windows (with WSL or Git Bash) and Linux/macOS, and provide guidance for PowerShell users if relevant.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
Biased
|
| 2025-08-19 00:01 | #85 | completed |
 Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
Flagged Code Snippets
## Operations using blob tags Blob index tags make data management and discovery easier. Blob index tags are user-defined key-value index attributes that you can apply to your blobs. Once configured, you can categorize and find objects within an individual container or across all containers. Blob resources can be dynamically categorized by updating their index tags without requiring a change in container organization. This approach offers a flexible way to cope with changing data requirements. You can use both metadata and index tags simultaneously. For more information on index tags, see [Manage and find Azure Blob data with blob index tags](storage-manage-find-blobs.md). > [!TIP] > The code sample provided below uses pattern matching to obtain text from an XML file having a known structure. The example is used to illustrate a simplified approach for adding blob tags using basic Bash functionality. The use of an actual data parsing tool is always recommended when consuming data for production workloads. The following example illustrates how to add blob index tags to a series of blobs. The example reads data from an XML file and uses it to create index tags on several blobs. To use the sample code, create a local *blob-list.xml* file in your *C:\temp* directory. The XML data is provided below. For more information, see the [az storage blob set-tier](/cli/azure/storage/blob#az-storage-blob-set-tier) reference.