Document Details
Backup Azure Sql Manage 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
Bias Types:
⚠️
windows_first
⚠️
missing_linux_example
Summary:
The documentation consistently assumes the SQL Server is running on a Windows VM and does not mention or provide guidance for Linux-based SQL Server VMs. All examples, resource names, and container naming conventions (such as 'mssqlserver', 'testSQLVM') implicitly reference Windows environments. There are no examples or notes for managing SQL Server on Linux VMs, nor any mention of Linux-specific considerations or differences.
Recommendations:
- Explicitly state whether the instructions apply to both Windows and Linux SQL Server VMs, or clarify if only Windows is supported.
- If Linux SQL Server VMs are supported, provide parallel examples and notes for Linux environments (e.g., naming conventions, prerequisites, differences in agent installation or backup support).
- Add a section or note about any limitations or differences when using Azure Backup for SQL Server on Linux VMs.
- Use more neutral naming in examples (e.g., avoid 'mssqlserver' if not Windows-specific) or provide both Windows and Linux variants.
- Reference relevant documentation for SQL Server on Linux in Azure VMs if available.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-09-11 00:00 | #108 | completed | ✅ Clean |
| 2025-08-11 00:00 | #77 | completed | ✅ Clean |
| 2025-08-10 00:00 | #76 | completed | ✅ Clean |
| 2025-08-09 00:00 | #75 | completed | ✅ Clean |
| 2025-08-08 00:00 | #74 | completed | ✅ Clean |
| 2025-08-07 00:00 | #73 | completed | ✅ Clean |
| 2025-08-06 00:00 | #72 | completed | ✅ Clean |
| 2025-08-05 00:00 | #71 | completed | ✅ Clean |
| 2025-08-03 00:00 | #69 | completed | ✅ Clean |
| 2025-08-01 00:00 | #67 | completed | ✅ Clean |
| 2025-07-31 00:00 | #66 | completed | ✅ Clean |
| 2025-07-30 00:00 | #65 | completed | ✅ Clean |
| 2025-07-29 00:01 | #64 | completed | ✅ Clean |
| 2025-07-28 00:00 | #63 | completed | ✅ Clean |
| 2025-07-27 00:00 | #62 | completed | ✅ Clean |
| 2025-07-26 00:01 | #61 | completed | ✅ Clean |
| 2025-07-25 00:00 | #60 | completed | ✅ Clean |
| 2025-07-24 00:00 | #59 | completed | ✅ Clean |
| 2025-07-23 00:00 | #58 | completed | ✅ Clean |
| 2025-07-22 00:01 | #57 | completed | ✅ Clean |
| 2025-07-21 00:00 | #56 | completed | ✅ Clean |
| 2025-07-19 13:51 | #54 | completed | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ✅ Clean |
| 2025-07-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ❌ Biased |
Flagged Code Snippets
Then use the [az backup protectable-item list](/cli/azure/backup/protectable-item#az-backup-protectable-item-list) cmdlet to list all the databases that have been discovered on your SQL instance. This list, however, excludes those databases on which backup has already been configured. Once the database to be backed-up is discovered, refer to [Enable backup on SQL database](backup-azure-sql-backup-cli.md#enable-backup-on-the-sql-database).