Backup
755
Total Pages
562
Linux-Friendly Pages
193
Pages with Bias
25.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
520 issues found
Showing 451-475 of 520 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The glossary is generally cross-platform and workload-neutral, but there are a few instances of Windows bias. The 'VSS (Windows Volume Shadow Copy Service)' entry links only to Windows documentation, and the 'Application consistent backup' definition mentions VSS first, with Linux alternatives referenced only parenthetically. The 'Snapshot' entry links to a Windows-specific disk snapshot page before mentioning file snapshots. Several backup agent and server entries (MARS, DPM, MABS) are Windows-centric, but these reflect actual product scope rather than documentation bias.
Recommendations
- For 'Application consistent backup', provide equal detail or links for Linux backup consistency mechanisms (e.g., pre/post scripts, fsfreeze, etc.), not just mention them parenthetically.
- For 'VSS', clarify that it is Windows-specific and, if relevant, mention Linux alternatives or link to documentation about Linux consistency methods.
- In the 'Snapshot' entry, link to both Windows and Linux disk snapshot documentation, or use a platform-neutral page if available.
- Where backup agents/servers are Windows-only (MARS, DPM, MABS), clarify their platform scope to avoid confusion, but do not flag as bias since these are inherently Windows products.
Create Pull Request
Backup
Back Up Azure VMs in a Recovery Services Vault
...b/main/articles/backup/backup-azure-arm-vms-prepare.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally presents a platform-neutral workflow for backing up Azure VMs, with both Windows and Linux VMs supported. However, in the 'Install the VM agent' section, instructions for Windows appear before Linux, which is a minor instance of Windows-first ordering. Both platforms are covered with appropriate detail, and no critical steps are Windows-only.
Recommendations
- Consider alternating the order of Windows and Linux instructions in sections where both are equally relevant, or present them in parallel tabs to avoid perceived preference.
- Where possible, clarify that all main backup workflows apply equally to both Windows and Linux VMs.
- Continue ensuring that Linux-specific details (such as package names or commands) are as explicit as Windows instructions.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The glossary is generally cross-platform and neutral, but there are minor signs of Windows bias: Windows-specific technologies (like VSS and MARS agent) are referenced directly, and Windows examples (e.g., VSS for application-consistent backup) are mentioned before Linux equivalents. Linux alternatives are referenced only briefly ("pre or post scripts for Linux") and not linked or explained in detail. Some backup features/tools (DPM, MABS) are Windows-centric, but these are marked as workload-specific and do not constitute bias under the provided guidelines.
Recommendations
- Where Windows technologies like VSS are referenced, provide equivalent Linux mechanisms (e.g., LVM snapshots, fsfreeze, application scripts) with links to relevant documentation.
- In sections mentioning backup agents or extensions (e.g., MARS agent), clarify Linux support or alternatives if applicable.
- When describing application-consistent backup, offer equal detail for Linux approaches (not just a parenthetical mention).
- Ensure that examples and references are balanced between Windows and Linux, or explicitly state when a feature is Windows-only.
Backup
Back Up an Azure Virtual Machine with Azure Extended Zones Portal
...ain/articles/backup/backup-azure-vms-extended-zones.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux instructions for installing the Azure VM agent, but the Windows instructions are listed first in the relevant table. All other instructions are platform-agnostic, as the process is performed through the Azure Portal UI and not via OS-specific tools or scripts. No PowerShell, Windows command-line, or Windows-only tools are mentioned outside of the agent installation section.
Recommendations
- Present Linux and Windows agent installation instructions in parallel or alternate which is shown first.
- Explicitly state that all portal-based steps apply equally to both Windows and Linux VMs.
- Where relevant, provide links to both Windows and Linux troubleshooting or reference guides.
Backup
Back up Azure Kubernetes Service by using Azure Backup
...cles/backup/azure-kubernetes-service-cluster-backup.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell as an alternative method for backup and restore, both in the introduction and in the 'Next steps' section, without mentioning Azure CLI or Bash equivalents. There are no Linux/macOS-specific instructions or examples, and the only command-line example given uses kubectl (which is cross-platform). The documentation focuses on GUI (Azure portal) workflows, but when scripting is mentioned, it is Windows-centric.
Recommendations
- Include Azure CLI examples alongside or before Azure PowerShell examples for backup and restore operations.
- Explicitly mention that kubectl commands work on Linux/macOS and provide any OS-specific caveats if relevant.
- Add links to Linux/macOS-friendly guides or scripts where applicable.
- Ensure parity in 'Next steps' by listing Azure CLI documentation if available.
Backup
Azure Kubernetes Service (AKS) backup support matrix
...azure-kubernetes-service-cluster-backup-support-matrix.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation references Azure PowerShell alongside Azure CLI, Terraform, ARM, and Bicep as supported tools for backup and restore operations. Azure PowerShell is a Windows-centric tool, and its mention (including dedicated links for backup and restore) signals a Windows bias. There is no explicit mention of Linux/macOS equivalents for PowerShell, nor are there Bash or shell script examples. Additionally, the order of tools in the 'Next steps' section lists Azure PowerShell before ARM and Bicep, which may reinforce a Windows-first perception. However, the main backup extension itself only supports Ubuntu or Azure Linux node pools, and not Windows-based node pools, which is a technical limitation rather than a documentation bias.
Recommendations
- Provide explicit Bash or shell script examples for Linux/macOS users where PowerShell is referenced.
- Clarify that Azure CLI and Terraform are cross-platform and recommend them for Linux/macOS users.
- Reorder tool references in 'Next steps' to list cross-platform tools first (e.g., Azure CLI, Terraform) and note platform specificity for PowerShell.
- Add a note that Azure PowerShell is primarily for Windows and suggest alternatives for Linux/macOS users.
Backup
Tutorial - Restore a VM with Azure CLI
...ocs/blob/main/articles/backup/tutorial-restore-disk.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is primarily focused on Azure CLI, which is cross-platform and suitable for both Linux and Windows users. However, there is a notable reference to PowerShell and a link to a PowerShell-based tutorial early in the page, and some terminology (such as 'container-name' and 'item-name' referring to VMs) may be more familiar to Windows/Azure users. The only explicit mention of an alternative platform is the PowerShell link, which is presented before the CLI instructions. All command examples are in Azure CLI, which is not Windows-specific, and there are no PowerShell or Windows command examples in the main content. There are no Linux/macOS-specific instructions or examples, but the CLI commands are applicable across platforms.
Recommendations
- Move or rephrase the PowerShell reference so it does not appear before the CLI instructions, or add a similar reference for Bash/shell scripting if relevant.
- Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and consider adding a brief note or section for common Linux/macOS shell environments.
- If there are any platform-specific caveats (e.g., path handling, authentication differences), mention them.
- Consider adding a short example of running these commands in a Bash shell to reinforce cross-platform parity.
Backup
Monitor Azure Backup protected workloads
...les/backup/backup-azure-monitoring-built-in-monitor.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-centric backup tools (DPM, MABS, MARS) and linking to a 'manage-windows-server' page for Recovery Services vault management. There are no explicit Linux or macOS examples, and Windows tools are mentioned exclusively when discussing backup item visibility and naming conventions.
Recommendations
- Include equivalent Linux backup agent/tool references (e.g., Azure Backup for Linux VMs, Azure CLI usage for Linux workloads).
- Provide links to documentation pages focused on Linux backup management, not just Windows Server.
- Add examples or notes for Linux/macOS users where backup item management or monitoring differs.
- Clarify whether features and limitations (such as naming conventions) apply to Linux workloads.
Backup
Quickstart - Back up a VM with the Azure portal by using Azure Backup
...cs/blob/main/articles/backup/quick-backup-vm-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page presents a minor Windows bias by referencing Windows VM creation first and listing Windows agent installation instructions before Linux. However, both Windows and Linux instructions are present and equally detailed, and the overall process is platform-neutral as it is performed via the Azure portal.
Recommendations
- Provide links to both Windows and Linux VM creation guides in the introduction, not just Windows.
- Alternate the order of Windows and Linux instructions in the VM agent installation section, or present them side-by-side.
- Explicitly state that the Azure portal process applies equally to both Windows and Linux VMs at the beginning of the article.
Backup
What is Azure Kubernetes Service (AKS) Backup?
...les/backup/azure-kubernetes-service-backup-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing 'Back up AKS by using Azure PowerShell' as the first related content link, ahead of the Linux-friendly Azure CLI restore guide. There is also an implicit emphasis on PowerShell in the related content, which is a Windows-centric tool, while Linux/macOS users typically use Azure CLI or Bash. However, the main body of the documentation avoids platform-specific instructions and examples, focusing on Kubernetes-native YAML and Azure portal workflows.
Recommendations
- Reorder related content links to list Azure CLI and cross-platform tools before PowerShell.
- Add explicit backup instructions using Azure CLI or Bash in the main documentation, not just in related content.
- Ensure all examples and walkthroughs are available for both PowerShell and CLI/Bash, with equal prominence.
- Clarify that both Windows and Linux/macOS users can perform all operations, and link to platform-specific guides where relevant.
Backup
Azure Kubernetes Service (AKS) backup support matrix
...azure-kubernetes-service-cluster-backup-support-matrix.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation references Azure PowerShell as a supported method for backup and restore operations, and lists it alongside Azure CLI, ARM, Bicep, and Terraform in the 'Next steps' section. However, there is no mention of Linux/macOS-specific tools or shell examples (such as Bash), nor is there explicit guidance for Linux users in scenarios where PowerShell is referenced. The documentation does not provide parity for Linux-native command-line usage, and PowerShell is listed before ARM/Bicep/Terraform in the backup/restore instructions, which may imply a Windows-first approach.
Recommendations
- Add explicit Bash or Linux shell examples for backup and restore operations using Azure CLI.
- Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS users.
- Reorder examples in the 'Next steps' section to list Azure CLI before PowerShell, emphasizing cross-platform tools.
- If PowerShell is referenced, note that it is available on Linux/macOS, or provide alternative instructions for those platforms.
- Include a statement on platform compatibility for all listed tools.
Backup
Azure Kubernetes Service (AKS) backup using Azure Backup prerequisites
...kup/azure-kubernetes-service-cluster-backup-concept.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell as a primary method for backup and restore operations, mentioning it before Azure CLI in some places, and omitting explicit Linux/macOS command-line examples. While Azure CLI is referenced, there are no direct bash or Linux-specific instructions, and PowerShell is highlighted as a main automation tool, which is more native to Windows environments.
Recommendations
- Ensure Azure CLI examples are provided and shown before or alongside PowerShell examples, as CLI is cross-platform.
- Add explicit bash/Linux/macOS command-line instructions or screenshots where relevant.
- Clarify that all Azure CLI commands work on Linux/macOS and Windows, and provide parity in walkthroughs.
- Avoid listing PowerShell as the primary or only automation method; present CLI and PowerShell equally.
- Where portal instructions are given, note that the portal is OS-agnostic.
Backup
Back up Azure Database for PostgreSQL - Flexible Server using Azure CLI
...p/back-up-azure-database-postgresql-flex-backup-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation primarily uses Azure CLI commands, which are cross-platform, but there is a notable Windows bias in the example for submitting the backup request: the file path is given in Windows format ('.\OSSBkpInstance.JSON') rather than the Linux/macOS equivalent ('./OSSBkpInstance.JSON'). There are no explicit Linux/macOS examples or notes about platform differences, and the only shell explicitly mentioned is 'bash' in one section, but the rest of the commands do not clarify shell compatibility. No PowerShell-specific commands or Windows-only tools are present, but the file path notation may cause confusion for Linux/macOS users.
Recommendations
- Provide both Windows and Linux/macOS file path examples when referencing files (e.g., '.\OSSBkpInstance.JSON' and './OSSBkpInstance.JSON').
- Add a note clarifying that Azure CLI is cross-platform and that file paths differ between Windows and Linux/macOS.
- Explicitly mention shell compatibility for each command block (e.g., 'bash', 'cmd', 'PowerShell', 'zsh').
- Include at least one Linux/macOS-specific example or screenshot to demonstrate parity.
Backup
Back Up Azure VMs in a Recovery Services Vault
...b/main/articles/backup/backup-azure-arm-vms-prepare.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains parity between Windows and Linux, especially in the 'Install the VM agent' section, where both platforms are covered. However, the Windows instructions are presented first in the table, which is a subtle form of Windows-first bias. There are no PowerShell-heavy examples, exclusive mention of Windows tools, or missing Linux examples. All procedures are portal-based and platform-agnostic.
Recommendations
- Alternate the order of Windows and Linux instructions in tables or sections to avoid implicit prioritization.
- Explicitly state that all steps are applicable to both Windows and Linux VMs unless otherwise noted.
- Where possible, provide CLI or script examples for both platforms, especially for advanced users.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely platform-neutral, focusing on REST API usage and JSON request/response bodies. However, there is minor evidence of Windows bias: in the Cross Region Restore section, example recovery points and metadata repeatedly use 'osType': 'Windows' and 'OsType': 'Windows', with no mention or example of Linux VMs. This could imply Windows is the default or primary scenario considered.
Recommendations
- Include example responses and request bodies for Linux VMs (e.g., with 'osType': 'Linux'), especially in sections where VM OS type is shown.
- Add clarifying notes that the REST API applies equally to both Windows and Linux VMs, and highlight any differences if they exist.
- Where metadata or configuration is shown (e.g., VMConfig.json), provide Linux-specific sample values or mention Linux scenarios.
- Ensure that documentation language and examples do not imply Windows is the default or only supported OS.
Backup
Back up Azure Disks using Azure Data Protection REST API.
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-disks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely platform-neutral, focusing on REST API calls and HTTP requests, which are usable from any OS. However, there is a subtle Windows bias in the 'Assign permissions' section, where the link for assigning permissions points to a PowerShell-based guide ('backup-managed-disks-ps.md'), and PowerShell is mentioned before Azure CLI. In the 'Next steps' section, PowerShell is listed before CLI, which may suggest a preference for Windows tooling.
Recommendations
- Ensure that all referenced guides for prerequisite steps (such as assigning permissions) include both Azure CLI and PowerShell instructions, and link to both.
- In lists of tools or next steps, alternate the order (e.g., CLI before PowerShell) or group them together as 'Azure CLI/PowerShell' to avoid perceived preference.
- Explicitly state that all REST API operations can be performed from any OS using standard HTTP tools (curl, Postman, etc.), and provide example commands for Linux/macOS environments where appropriate.
- Add a short section or note clarifying cross-platform compatibility for all steps.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists all supported VM SKUs for Azure Backup policies, with Windows-based SKUs presented first and in much greater detail than Linux-based SKUs. The Windows section is extensive, with many variants and editions, while Linux distributions are listed after all Windows entries and with less granularity. No examples, tools, or instructions are given, but the ordering and detail favor Windows.
Recommendations
- Reorder the table or split it into separate sections for Windows and Linux to give equal prominence.
- Provide more detailed breakdowns of Linux SKUs, including variants and supported features, matching the granularity given to Windows.
- Add explicit notes about Linux backup feature parity, limitations, and any platform-specific considerations.
- Consider listing Linux SKUs first or alternating entries to avoid implicit prioritization.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation mentions BitLocker for Windows VMs before DM-Crypt for Linux VMs when describing in-guest encryption, and references SQL Server and TDE (Transparent Data Encryption) features that are primarily Windows-centric. There are no explicit Linux or macOS command examples, and Windows technologies are named first or exclusively in some contexts.
Recommendations
- Present Linux and Windows encryption technologies in parallel, e.g., 'ADE uses BitLocker for Windows VMs and DM-Crypt for Linux VMs' rather than listing Windows first.
- Include examples or references for Linux backup and restore scenarios, especially for disk encryption and database backup/restore.
- Add links to Linux-specific documentation for DM-Crypt and other relevant tools.
- Clarify cross-platform support for features like TDE and provide guidance for Linux-based SQL Server deployments if applicable.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation primarily describes backing up Azure Managed Disks using the Azure portal, which is cross-platform. However, when mentioning automation or scripting, PowerShell is listed before CLI, and there are references to PowerShell scripts without explicit Linux/macOS shell examples. There are no screenshots or walkthroughs for Linux/macOS-specific tools or workflows, and PowerShell is implicitly prioritized for scripting tasks.
Recommendations
- List Azure CLI before or alongside PowerShell when mentioning automation or scripting options.
- Provide explicit Bash or shell script examples for Linux/macOS users where scripting is discussed.
- Add screenshots or step-by-step instructions for Azure CLI usage in Linux/macOS environments.
- Clarify that all portal instructions are cross-platform and note any OS-specific differences if present.
Backup
Back Up a PostgreSQL Databases by Using the Azure CLI
...ocs/blob/main/articles/backup/backup-postgresql-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is primarily cross-platform and uses Azure CLI (which works on Windows, Linux, and macOS) for all main backup operations. However, there is a notable Windows bias in the explanations: PowerShell objects and workflows are referenced first and described in detail, while Linux/macOS equivalents (such as file-based editing in CLI) are mentioned as alternatives. Some example paths use Windows-style (e.g., .\file.json), and PowerShell is presented as the default or primary method for policy modification, with CLI described as a workaround for non-Windows users.
Recommendations
- Present CLI and PowerShell workflows in parallel, not with PowerShell first or as the default.
- Use platform-neutral file path examples (e.g., ./file.json instead of .\file.json).
- Explicitly mention that Azure CLI works on Linux/macOS and provide Bash examples where appropriate.
- Avoid describing PowerShell as the 'default' and CLI as a workaround; treat both as first-class options.
- Add a short section clarifying cross-platform support and parity.
Backup
Azure Resource Manager and Bicep files
...lob/main/articles/backup/backup-rm-template-samples.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists multiple Azure Resource Manager and Bicep templates for backup scenarios. While most templates are platform-agnostic, the only OS-specific example provided is for deploying a Windows Server VM with backup enabled. There is no equivalent example for Linux VMs, nor is there mention of Linux-specific backup scenarios. This subtly prioritizes Windows use cases and may imply Windows is the default or preferred platform for backup operations.
Recommendations
- Add examples and templates for deploying and backing up Linux VMs, such as Ubuntu or CentOS, alongside the Windows Server VM example.
- Explicitly state that the templates are applicable to both Windows and Linux VMs where relevant.
- Include notes or links to documentation for Linux-specific backup considerations or troubleshooting.
- Ensure parity in OS coverage by providing SQL Server on Linux backup scenarios if supported.
Backup
Manage Backups with Azure role-based access control
...docs/blob/main/articles/backup/backup-rbac-rs-vault.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific backup agents and tools (e.g., 'Azure Backup agent client UI', 'System Center Data Protection Manager UI', 'Azure Backup Server UI', and 'on-premises Windows Server/client/SCDPM or Azure Backup Server') without mentioning Linux equivalents. Windows backup scenarios are explicitly called out in the role mapping tables, while Linux backup scenarios (such as on-premises Linux servers) are not addressed. Additionally, the 'Next steps' section lists PowerShell before Azure CLI, which is more cross-platform, and does not provide Bash or Linux shell examples.
Recommendations
- Include references to Linux backup agents or clarify support for Linux on-premises servers in the role mapping tables.
- Mention Linux-compatible tools and workflows (such as Azure CLI, Bash scripts, or Linux backup agents) alongside Windows tools.
- When listing command-line options, present Azure CLI (cross-platform) before PowerShell and provide explicit Bash/Linux shell examples where relevant.
- Add a section or note about role requirements for Linux-based backup scenarios if supported.
- Avoid using Windows-centric terminology exclusively; ensure parity in examples and tool mentions.
Backup
Tutorial - Configure vaulted backup for Azure Blobs using Azure Backup
...main/articles/backup/blob-backup-configure-tutorial.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation references Azure PowerShell as the first option for restoring Azure Blobs, followed by Azure CLI and REST API. This ordering and explicit mention of PowerShell may suggest a Windows-centric approach, as PowerShell is traditionally associated with Windows environments. However, Azure CLI and REST API options are also provided, which are cross-platform. There are no explicit Linux/macOS examples or guidance, and no mention of platform-specific considerations.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as CLI is more universally available across platforms.
- Explicitly mention that Azure CLI and REST API are cross-platform and suitable for Linux/macOS users.
- Provide example commands for both PowerShell and Azure CLI in the main tutorial, not just in related content.
- Add notes or sections addressing any platform-specific steps or considerations for Linux/macOS users.
Backup
Quickstart - Configure vaulted backup for Azure Blobs using Azure Backup
...ob/main/articles/backup/blob-backup-configure-quick.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page lists Azure PowerShell as a primary method for restoring Azure Blobs before mentioning Azure CLI and REST API. This ordering, along with the explicit mention of PowerShell, may suggest a Windows-centric approach, as PowerShell is most commonly associated with Windows environments. There are no Linux/macOS-specific instructions or examples, and the documentation does not clarify cross-platform compatibility for the CLI or REST API methods.
Recommendations
- Explicitly state that Azure CLI and REST API are cross-platform and suitable for Linux/macOS users.
- Provide example commands for both Azure PowerShell and Azure CLI side-by-side, or indicate which are best for which platforms.
- Consider listing Azure CLI before PowerShell to avoid implicit Windows-first bias.
- Add a note or section addressing Linux/macOS users and any platform-specific considerations.
Backup
Manage Azure Files backups with the Azure CLI
...ocs/blob/main/articles/backup/manage-afs-backup-cli.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is largely cross-platform, focusing on Azure CLI commands that work on Windows, Linux, and macOS. However, there is a notable Windows bias in the Vault-Standard tier section, where the example output includes a Windows-style command prompt path (C:\Users\testuser\Downloads\CLIForAFS\azure-cli>) and the use of Windows file redirection syntax (> vaultdemopol.json) without clarifying Linux/macOS equivalents. Additionally, Windows/PowerShell and Azure Portal management options are mentioned before REST API, with no explicit mention of Linux shell alternatives or parity.
Recommendations
- Provide Linux/macOS equivalent command-line examples for file redirection (e.g., using > in Bash/zsh).
- Avoid including Windows-specific command prompt paths in example outputs, or provide cross-platform alternatives.
- Explicitly state that all Azure CLI commands work on Linux/macOS and Windows, and mention any OS-specific caveats if present.
- When listing management options, mention Linux shell usage or parity alongside Windows/PowerShell and Azure Portal.
- Add a short note or section on cross-platform usage, especially for file operations and environment setup.