[PLEASE SQUASH] Common issues with automated backups due to customer actions (#34518)

* Common issues with automated backups due to customer actions

* Apply suggestions from code review

Co-authored-by: Randolph West MSFT <97149825+rwestMSFT@users.noreply.github.com>

* Update automated-backups-overview.md

* rewording of the backup failures due to full tlog

* Update azure-sql/managed-instance/automated-backups-overview.md

Co-authored-by: William Assaf MSFT <74387232+WilliamDAssafMSFT@users.noreply.github.com>

* Update automated-backups-overview.md

* Apply suggestions from code review

a few edits

---------

Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com>
Co-authored-by: Bo wen Yang <160521015+Albertyang0@users.noreply.github.com>
Co-authored-by: William Assaf MSFT <74387232+WilliamDAssafMSFT@users.noreply.github.com>
Co-authored-by: Randolph West MSFT <97149825+rwestMSFT@users.noreply.github.com>
Co-authored-by: Masha Thomas (MSFT) <32783170+MashaMSFT@users.noreply.github.com>

Author: 6 people

azure-sql/managed-instance/automated-backups-overview.md

@@ -2,10 +2,10 @@
 title: Automatic, Geo-Redundant Backups
 titleSuffix: Azure SQL Managed Instance
 description: Learn how Azure SQL Managed Instance automatically backs up all databases and provides point-in-time restore capability.
-author: Stralle
-ms.author: strrodic
-ms.reviewer: mathoma, wiassaf, danil, randolphwest
-ms.date: 05/27/2025
+author: dinethi
+ms.author: dinethi
+ms.reviewer: mathoma, wiassaf, mlandzic, strrodic, danil, randolphwest
+ms.date: 06/26/2025
 ms.service: azure-sql-managed-instance
 ms.subservice: backup-restore
 ms.topic: conceptual
@@ -288,6 +288,17 @@ Microsoft is fully responsible for keeping and rotating keys for databases with
 
 Automatic backups stored in Azure-managed storage accounts are automatically encrypted by Azure storage. Learn more about [Azure Storage encryption for data at rest](/azure/storage/common/storage-service-encryption).
 
+## Common issues with automated backups due to customer actions
+
+While Azure SQL Managed Instance provides automated backups to ensure data protection and recovery, certain customer-side configurations or actions can lead to backup failures. Common scenarios include:
+
+- Insufficient storage for the SQL managed instance. If the storage allocated to your instance is full, automated backups aren't taken.
+- User-defined jobs or scripts that kill system processes can stop automated backup operations.
+- Incorrect DNS settings can prevent the SQL managed instance from accessing required Azure endpoints, including those used for backups, leading to backup failures.
+- The transaction log could fill due to prevented truncation from misconfigured replication, CDC or full storage (at the instance level). If the transaction log is full and can't be truncated, full and differential backups fail, but log backups still succeed without truncating the log file.
+
+To ensure reliable backups, it's important to monitor system resources, validate configuration settings, and avoid interfering with built-in service operations. Make sure to monitor allocated storage, have correct DNS settings, and review custom jobs and replication configurations.
+
 ## Backup integrity
 
 All database backups are taken with the CHECKSUM option to provide additional backup integrity. Automatic testing of automated database backups by the Azure SQL engineering team isn't currently available for Azure SQL Managed Instance. Schedule test backup restoration and DBCC CHECKDB on your databases in SQL Managed Instance around your workload.