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 1501-1525 of 1657 flagged pages
Storage
Static website hosting in Azure Storage
.../articles/storage/blobs/storage-blob-static-website.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists both Windows and cross-platform tools for uploading content (Azure CLI, AzCopy, Storage Explorer, Portal, VS Code extension, Azure Pipelines), but the Azure PowerShell module is mentioned before AzCopy and Storage Explorer. Additionally, PowerShell is given as a primary example tool alongside CLI, which may suggest a slight Windows bias. No Linux/macOS-specific examples or tools are omitted, but the ordering and inclusion of PowerShell as a top-level option could create friction for non-Windows users.
Recommendations
- List cross-platform tools (Azure CLI, AzCopy, Storage Explorer, Portal, VS Code extension) before Windows-specific tools like PowerShell.
- Explicitly note that Azure CLI, AzCopy, and Storage Explorer are available on Linux/macOS and provide example commands for those platforms.
- Where PowerShell is mentioned, clarify that it is primarily for Windows users and suggest CLI/AzCopy for Linux/macOS.
- Consider including a table or section that maps recommended tools to OS platforms for clarity.
Create Pull Request
Storage
Map a custom domain to an Azure Blob Storage endpoint
...n/articles/storage/blobs/storage-custom-domain-name.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all command-line steps, but PowerShell is consistently listed before CLI, and the CLI instructions are incorrectly labeled as 'PowerShell command' in several places. This ordering and labeling may create friction for Linux/macOS users, who are more likely to use Azure CLI. No Windows-only tools or patterns are present, and all instructions are accessible cross-platform, but the presentation favors Windows/PowerShell users.
Recommendations
- Correct the labeling of Azure CLI sections to avoid calling them 'PowerShell command'.
- Alternate or randomize the order of PowerShell and CLI tabs, or list CLI first in sections where Linux/macOS users are likely to be the audience.
- Add a short note clarifying that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Ensure that all examples and instructions are equally clear for both PowerShell and CLI users.
Storage
Blob Storage feature support in Azure storage accounts
...e/blobs/storage-feature-support-in-storage-accounts.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation lists both 'Blob Storage PowerShell commands' and 'Blob Storage Azure CLI commands' as supported features, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is listed immediately after CLI in both tables. There are no Linux/macOS-specific examples or tools (other than Blobfuse, which is Linux-only and appropriately included). No explicit Linux/macOS bias is present, but the inclusion and ordering of PowerShell may subtly reinforce Windows as a primary platform.
Recommendations
- Consider listing cross-platform tools (Azure CLI, REST API, SDKs) before platform-specific tools like PowerShell.
- Add explicit notes that PowerShell is available on Linux/macOS, or link to cross-platform installation guides.
- Where possible, provide example commands for both CLI and PowerShell, and clarify platform compatibility.
- Highlight Linux/macOS tools (such as Blobfuse) with equal prominence to PowerShell.
Storage
Quickstart: Azure Blob storage library - JavaScript
...icles/storage/blobs/storage-quickstart-blobs-nodejs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for both Windows and Linux when setting environment variables, but in several places, Windows tools (cmd, PowerShell) are mentioned before Linux equivalents. The authentication instructions include PowerShell as a sign-in option alongside Azure CLI and Visual Studio Code, but do not mention Linux-specific shells or tools. The initial project setup instructions list 'cmd, PowerShell, or Bash' as console options, but the order prioritizes Windows tools. Overall, Linux parity is present, but Windows tools and workflows are often listed first or given slightly more detail.
Recommendations
- List Bash (Linux/macOS) first or alongside Windows tools when mentioning console options.
- Include explicit instructions or examples for Linux/macOS shells (e.g., zsh, bash) where relevant, especially in authentication steps.
- Ensure parity in detail and order for Linux/macOS and Windows instructions throughout the documentation.
- When referencing Visual Studio Code, clarify that it is cross-platform and provide alternatives for Linux/macOS users if needed.
Storage
Quickstart: Azure Blob Storage library - .NET
...icles/storage/blobs/storage-quickstart-blobs-dotnet.md
Low Priority
View Details →
Detected Bias Types
Windows First
Visual Studio Heavy
Summary
The documentation provides both Visual Studio (Windows-centric) and .NET CLI (cross-platform) instructions for project creation and package installation. However, Visual Studio steps and screenshots are presented first and in more detail, which may signal a Windows-first bias. The CLI instructions do mention Bash and Visual Studio Code, but the overall flow and visuals prioritize Windows tooling. No critical steps are Windows-only, and Linux/macOS users can complete all tasks using the .NET CLI and VS Code.
Recommendations
- Present .NET CLI instructions before Visual Studio steps to emphasize cross-platform parity.
- Include explicit references to Linux/macOS environments in CLI instructions (e.g., show screenshots or terminal output from Bash/zsh).
- Add a note clarifying that all steps can be performed on Linux/macOS using the .NET CLI and VS Code.
- Balance screenshots: add VS Code or terminal screenshots alongside Visual Studio images.
- Where 'console window' is mentioned, clarify that Bash/zsh/Terminal are fully supported on Linux/macOS.
Storage
Quickstart: Azure Blob storage library - TypeScript
...ge/blobs/storage-quickstart-blobs-nodejs-typescript.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for both Windows and Linux when setting environment variables, and mentions Bash alongside cmd and PowerShell for console usage. However, in authentication instructions, Windows tools (Azure CLI, Visual Studio Code, PowerShell) are listed first and in more detail, with PowerShell given its own section. The instructions for running the code and opening the project also reference Visual Studio Code, which is cross-platform but more commonly associated with Windows. Overall, Linux/macOS users are supported, but Windows tools and patterns are presented first and more prominently.
Recommendations
- Present authentication methods in a neutral order, or explicitly mention Linux/macOS equivalents (e.g., Bash, Terminal, zsh) alongside Windows tools.
- Include explicit instructions for Linux/macOS users for opening the project (e.g., 'code .' works on all platforms, but mention alternatives if VS Code is not installed).
- When listing environment variable setup, consider showing Linux/macOS instructions first or side-by-side with Windows.
- Add a note that all steps work on Linux/macOS unless otherwise stated, and highlight any platform-specific caveats.
- Consider including screenshots or terminal prompts that reflect Linux/macOS environments as well as Windows.
Storage
Quickstart: Azure Blob Storage client library for Python
...icles/storage/blobs/storage-quickstart-blobs-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally provides cross-platform instructions, but there are minor signs of Windows bias. In authentication instructions, PowerShell is mentioned as a sign-in method alongside Azure CLI and Visual Studio Code, and Windows environment variable setting instructions are shown before Linux equivalents. PowerShell is given its own tab, while Bash is not. However, Linux instructions are present and functional throughout, and most commands are platform-neutral.
Recommendations
- Present Linux and Windows instructions in parallel or in a neutral order, rather than listing Windows first.
- Include Bash as a first-class sign-in tab alongside PowerShell, especially for authentication steps.
- When setting environment variables, present Linux and Windows instructions together, or default to Bash first if usage statistics support it.
- Explicitly state cross-platform compatibility for all CLI commands and code samples.
- Add a note that all examples work on Linux/macOS unless otherwise specified.
Storage
Quickstart: Deploy a static website on Azure Storage using Terraform
...e/blobs/storage-quickstart-static-website-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell example is included as a primary tab, and the CLI example is shown first. There is no explicit Linux/macOS bias, but PowerShell is a Windows-centric tool, and its inclusion may suggest a slight Windows preference. However, the main workflow uses Terraform, which is cross-platform, and the Azure CLI example is provided and shown first.
Recommendations
- Clarify that both Azure CLI and PowerShell commands work on Windows, Linux, and macOS (since Azure CLI is cross-platform and PowerShell Core is available on Linux/macOS).
- Consider adding a note that Azure CLI is recommended for Linux/macOS users.
- If possible, provide bash-specific examples for Linux/macOS users, especially for browser automation or scripting.
- Explicitly state platform compatibility for each example.
Storage
Configure cross-tenant customer-managed keys for an existing storage account
...r-managed-keys-configure-cross-tenant-existing-account.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for configuring cross-tenant customer-managed keys using the Azure portal, PowerShell, and Azure CLI. PowerShell examples are given before Azure CLI, and there is no mention of Linux/macOS-specific shell usage or considerations. While Azure CLI is cross-platform, the ordering and explicit PowerShell instructions may create a mild Windows bias.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS as well as Windows.
- Consider listing Azure CLI examples before PowerShell, as CLI is more universally accessible.
- Add a short note or section highlighting Linux/macOS compatibility and any OS-specific prerequisites (e.g., installation instructions for Azure CLI on Linux/macOS).
- If there are any platform-specific caveats (such as environment variable syntax differences), call them out.
Storage
GPv1 ZRS standard account retirement FAQ
...-zone-redundant-storage-migration-freq-asked-questions.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation mentions upgrade procedures via the Azure portal, CLI, or PowerShell, but PowerShell is referenced multiple times and is listed before CLI in some places. There are no explicit Linux/macOS-specific examples or guidance, and no mention of Bash or shell scripting. The upgrade process is described generically, but the repeated mention of PowerShell and lack of Linux/macOS parity in examples or troubleshooting creates a mild Windows bias.
Recommendations
- Provide explicit examples for both Azure CLI (cross-platform) and PowerShell, with CLI examples shown first or in parallel.
- Clarify that Azure CLI is fully supported on Linux/macOS and provide links or instructions for installation and usage on those platforms.
- Include troubleshooting steps or notes relevant to Linux/macOS users, especially for upgrade scenarios.
- Avoid listing PowerShell before CLI unless there is a technical reason (e.g., feature parity differences).
Storage
Set the default public network access rule: Azure Storage
.../common/storage-network-security-set-default-access.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for both Azure PowerShell and Azure CLI, but PowerShell is presented before CLI, and the PowerShell section is more detailed. PowerShell is a Windows-centric tool, while Azure CLI is cross-platform. No Linux/macOS-specific examples or notes are provided, and there is no mention of Bash scripting or Linux shell integration.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more widely used on Linux/macOS.
- Add explicit notes that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows (with limited cross-platform support).
- Include example Bash scripts or usage in Linux/macOS terminals to demonstrate parity.
- Clarify tool availability and recommend Azure CLI for non-Windows users.
Storage
Azure Storage encryption for data at rest
.../articles/storage/common/storage-service-encryption.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page contains minor Windows bias. It references BitLocker encryption as a comparison for Azure Storage encryption and links to the Windows-specific Cryptography API: Next Generation (CNG) documentation for more information about cryptographic modules. These references may be less relevant or familiar to Linux/macOS users. However, the technical content and instructions are platform-neutral and do not rely on Windows-only tools or patterns.
Recommendations
- When comparing Azure Storage encryption, also mention Linux/macOS equivalents (e.g., LUKS, dm-crypt) alongside BitLocker to provide parity for non-Windows users.
- Supplement or replace the reference to Windows CNG documentation with links to general cryptographic standards (e.g., NIST FIPS 140-2, AES documentation) or Azure's own platform-neutral cryptography documentation.
- Ensure that all examples and guidance remain platform-neutral, and avoid implying that Windows tools or patterns are the default or primary approach unless strictly necessary.
Storage
Require secure transfer to ensure secure connections
...cles/storage/common/storage-require-secure-transfer.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for configuring secure transfer on Azure Storage accounts. However, the PowerShell section appears before the Azure CLI section, and the PowerShell instructions are more detailed, including module installation and connection steps. This ordering and emphasis may create a slight Windows bias, as PowerShell is primarily a Windows tool (though it is available cross-platform). No Linux/macOS-specific tools or examples (such as Bash scripts or SDK usage from Linux) are provided, but the CLI example is platform-neutral.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is platform-neutral and widely used on Linux/macOS.
- Add explicit notes that both PowerShell and CLI are available cross-platform, with installation links for Linux/macOS users.
- Include a brief example using a REST API call via curl, which is common on Linux/macOS.
- Clarify that all programmatic methods (SDKs, REST API, CLI) work on Linux/macOS, and link to relevant installation guides.
Storage
Copy blobs between Azure storage accounts with AzCopy v10
...ticles/storage/common/storage-use-azcopy-blobs-copy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides clear guidance for both Windows and non-Windows users regarding quoting conventions in AzCopy commands. However, the tip about quoting always mentions Windows Command Shell (cmd.exe) first, and does not provide explicit Linux/macOS command-line examples or mention shells like Bash or Zsh by name. All command examples use single quotes, which are correct for Linux/macOS, but the documentation does not show a corresponding double-quoted example for Windows users. There is no evidence of PowerShell-specific commands, Windows-only tools, or missing Linux examples, but the ordering and phrasing slightly favor Windows-first presentation.
Recommendations
- Explicitly mention Linux/macOS shells (e.g., Bash, Zsh) when describing quoting conventions.
- Provide at least one example command using double quotes for Windows cmd.exe users.
- Consider alternating the order in which Windows and non-Windows platforms are referenced, or provide a table summarizing quoting conventions for each shell.
- Clarify that AzCopy is fully cross-platform and that all examples work on Linux/macOS unless otherwise noted.
Storage
Authorize access for AzCopy with a managed identity
...ommon/storage-use-azcopy-authorize-managed-identity.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux (bash) and Windows (PowerShell) examples for environment variable configuration, generally in parallel tabs. However, in some sections (notably 'Authorize with Azure CLI'), the Windows example uses PowerShell and introduces a different value for AZCOPY_AUTO_LOGIN_TYPE ('PSCRED' vs 'AZCLI'), which may create confusion or friction for Linux users. Additionally, PowerShell is consistently used for Windows examples, and Windows tabs are sometimes presented before Linux equivalents. There is no evidence of missing Linux examples or exclusive mention of Windows tools.
Recommendations
- Clarify the difference between AZCOPY_AUTO_LOGIN_TYPE values ('AZCLI' for Linux, 'PSCRED' for Windows) and why they differ. Consider providing a brief explanation for Linux users.
- Ensure Linux and Windows tabs are presented in a consistent order (e.g., Linux first, then Windows) to avoid subtle prioritization.
- Where PowerShell is used for Windows examples, consider mentioning that CMD syntax may also be used, or provide a CMD example if relevant.
- Review and harmonize terminology so that Linux and Windows instructions are equally clear and complete.
Storage
Copy from Google Cloud Storage to Azure Storage with AzCopy
...cles/storage/common/storage-use-azcopy-google-cloud.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides OS-specific instructions for setting environment variables and quoting conventions, but Windows examples and notes are presented first in relevant sections. However, Linux and macOS equivalents are also included, and all AzCopy command examples are OS-agnostic.
Recommendations
- Present OS instructions in alphabetical order (e.g., Linux, macOS, Windows) or group Linux/macOS together before Windows to avoid implicit prioritization.
- Explicitly state that AzCopy commands work identically on Linux, macOS, and Windows, and provide any OS-specific caveats if they exist.
- Where quoting conventions are discussed, consider showing Linux/macOS first or equally, rather than noting Windows exceptions after the fact.
Storage
Transfer data to or from Azure Files by using AzCopy v10
...in/articles/storage/common/storage-use-azcopy-files.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows (SMB) and Linux (NFS) examples for all major AzCopy operations, using tabbed sections for each. However, in most sections, Windows-style paths (e.g., C:\myDirectory) and SMB examples are shown first, with Linux/NFS examples following. There are frequent reminders about quoting conventions for Windows Command Shell, but no explicit bash or Linux shell command examples beyond the path style. The overall structure and example ordering slightly favor Windows users, but Linux parity is maintained throughout.
Recommendations
- Alternate the order of examples so that Linux/NFS examples are shown first in some sections, or present both examples side-by-side.
- Add explicit bash shell command examples, including quoting and environment variable usage for Linux/macOS.
- Include a brief section at the top summarizing platform-specific considerations (e.g., quoting, permissions) for Linux/macOS users.
- Where possible, clarify that AzCopy commands work identically on Linux/macOS and Windows, and highlight any differences in flags or behavior.
Storage
Optimize the performance of AzCopy v10 with Azure Storage
...articles/storage/common/storage-use-azcopy-optimize.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for setting environment variables, but Windows (PowerShell/cmd) instructions are often shown before Linux equivalents. There is a tip about quoting conventions that prioritizes Windows Command Shell (cmd.exe) over other shells. However, Linux-specific optimization (concurrent local scanning) is mentioned, and most instructions are cross-platform. The bias is minor and does not prevent Linux/macOS users from completing any tasks.
Recommendations
- Present Linux and Windows examples side-by-side or in tabs, ensuring neither is prioritized in order or prominence.
- Expand tips to explicitly mention macOS where relevant (e.g., quoting conventions, environment variable setting).
- Where quoting conventions are discussed, clarify for bash/zsh/fish and PowerShell/cmd, rather than 'all command shells except Windows Command Shell'.
- Consider adding a short section confirming AzCopy parity across platforms and linking to OS-specific installation/configuration guides.
Storage
Copy or move data to Azure Storage by using AzCopy v10
...main/articles/storage/common/storage-use-azcopy-v10.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally presents AzCopy as a cross-platform tool and includes installation instructions for Windows, Linux, and macOS. However, there is a subtle Windows bias: the only example command for using AzCopy (with a SAS token) uses a Windows-style path (C:\local\path) and does not provide a Linux/macOS equivalent. Additionally, the example is shown with Windows syntax first, and there is no explicit Linux/macOS command example or mention of Linux-specific path conventions.
Recommendations
- Provide example AzCopy commands using Linux/macOS path syntax (e.g., /home/user/path) alongside Windows examples.
- Explicitly mention how to run AzCopy commands in Linux/macOS shells, including path conventions and any differences in command invocation.
- Where examples use Windows paths or conventions, add parallel Linux/macOS examples for parity.
- Clarify that AzCopy commands work identically across platforms, but path syntax differs.
Storage
Copy data from Amazon S3 to Azure Storage by using AzCopy
.../main/articles/storage/common/storage-use-azcopy-s3.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Windows and Linux/macOS instructions for setting AWS credentials, but Windows tools (PowerShell and Command Prompt) are listed first in the table. There is a specific tip about quoting conventions that gives precedence to Windows Command Shell (cmd.exe) over other shells, but it does mention Linux/macOS conventions. All AzCopy command examples are shell-agnostic and work across platforms. No Linux/macOS examples are missing, but Windows tools and patterns are mentioned first.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions in tables and examples, or alternate the order to avoid implicit prioritization.
- Clarify quoting conventions for all major shells (bash, zsh, PowerShell, cmd.exe) with equal prominence.
- Where possible, provide explicit shell examples for Linux/macOS (e.g., bash, zsh) and Windows (PowerShell, cmd.exe) to ensure parity.
- Add a note at the start confirming AzCopy is fully cross-platform and all examples apply equally to Linux, macOS, and Windows unless otherwise stated.
Storage
Enforce a Minimum Required Version of Transport Layer Security (TLS)
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-minimum-version.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits mild Windows bias in several ways: the PowerShell example is presented before the Azure CLI example, and PowerShell is referenced as a primary automation tool. There is a tip referencing Azure Storage's reliance on the Windows SSL implementation, which may be confusing or less relevant for Linux users. However, the core configuration steps (Azure Portal, Azure CLI, ARM templates) are all cross-platform, and Linux/macOS users can fully complete the documented tasks using Azure CLI and templates.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more widely used by Linux/macOS users.
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for non-Windows environments.
- Add a brief note explaining the relevance (or irrelevance) of the Windows SSL implementation for Linux/macOS clients, especially in the context of the OpenSSL tip.
- Where screenshots or instructions reference Windows-specific tools or UI, consider adding notes or alternatives for Linux/macOS users if applicable.
Storage
Connect Azure Elastic SAN to Azure Kubernetes over iSCSI
...rticles/storage/elastic-san/elastic-san-connect-aks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists both Azure PowerShell (Windows-centric) and Azure CLI (cross-platform) methods for retrieving volume information, but presents the PowerShell example first. All other steps use cross-platform tools (kubectl, curl, YAML manifests) and do not show Windows-specific patterns or tools. No Linux/macOS examples are missing, and the instructions are generally platform-neutral except for the ordering of PowerShell before CLI.
Recommendations
- Present Azure CLI examples before Azure PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly note that Azure CLI works on Windows, Linux, and macOS, and is recommended for non-Windows environments.
- Consider grouping PowerShell and CLI examples together, or providing tabs for each to make parity clear.
Storage
Azure Elastic SAN configuration best practices
...cles/storage/elastic-san/elastic-san-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally provides parity between Windows and Linux, offering best practices, configuration steps, and examples for both platforms. However, there is a mild Windows bias: Windows examples and instructions are often presented before Linux equivalents, and links to enabling Accelerated Networking reference Azure PowerShell before Azure CLI. Windows-specific tools (e.g., Registry Editor, iSCSI Initiator app) are described in detail, sometimes with screenshots, while Linux instructions are more command-line focused and less visual. The use of PowerShell and Windows GUI tools is emphasized in some sections.
Recommendations
- Alternate the order of Windows and Linux sections so Linux instructions are sometimes presented first.
- Provide equivalent visual aids (screenshots) for Linux configuration steps where possible, not just Windows.
- When referencing enabling features (e.g., Accelerated Networking), link to both Azure PowerShell and Azure CLI instructions equally and mention Linux CLI usage explicitly.
- Ensure that Linux configuration steps are as detailed and user-friendly as Windows steps, including troubleshooting tips and references to Linux documentation.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Python/CLI) examples for disconnecting volumes, and both Azure PowerShell and Azure CLI commands for deleting resources. However, Windows/PowerShell examples are consistently presented before Linux/CLI equivalents, and PowerShell is given equal prominence to Azure CLI throughout, which may create a slight perception of Windows bias.
Recommendations
- Alternate the order of Windows/PowerShell and Linux/CLI examples in each section, or present them side-by-side to avoid implicit prioritization.
- Explicitly state that both PowerShell and CLI approaches are fully supported and equivalent, to reassure non-Windows users.
- Consider adding macOS-specific notes if there are any platform caveats, or clarify that Linux instructions apply to macOS where appropriate.
- Ensure that script references (e.g., disconnect scripts) are equally maintained and documented for both platforms.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all operations, but PowerShell examples are consistently listed before CLI examples. This ordering can subtly signal a Windows-first approach. Additionally, PowerShell is a Windows-native tool (though available on Linux), and there are no explicit Linux/macOS shell examples (e.g., bash scripts), nor is there mention of Linux-specific considerations beyond a brief reference to fsfreeze for application consistency.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux/macOS users.
- Explicitly mention that Azure CLI commands work natively on Linux/macOS and Windows, while PowerShell may require installation on non-Windows platforms.
- Provide brief bash script examples for common tasks, or link to guidance on using Azure CLI in Linux/macOS environments.
- Expand the section on application-consistent backups to include more Linux tooling (e.g., LVM snapshots, database-specific tools) for parity with the Windows VSS mention.