Merge pull request #25018 from ktoliver/masha-1

edit pass: 3 Azure SQL Managed Instance articles (2009693)

Author: ShawnJackson

azure-sql/managed-instance/auto-failover-group-standby-replica-how-to-configure.md

@@ -1,6 +1,6 @@
 ---
 title: Backup transparency for backup history
-description: "Use backup transparency to view your backup history for your  Azure SQL Managed Instance. "
+description: Learn how to use backup transparency to view the backup history of Azure SQL Managed Instance. 
 author: MilanMSFT
 ms.author: mlazic
 ms.date: 11/16/2022
@@ -10,62 +10,61 @@ ms.topic: conceptual
 ms.custom:
 ---
 # Backup transparency in Azure SQL Managed Instance
-[!INCLUDE[appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
 
-This article describes backup transparency in Azure SQL Managed Instance. 
+[!INCLUDE[appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
 
-## Overview 
+In this article, learn how to use backup transparency in Azure SQL Managed Instance to view the backup history of your managed instance.
 
-The [msdb database](/sql/relational-databases/databases/msdb-database) enables backup transparency in Azure SQL Managed Instance by making backup history tables queryable. However, there are a few key differences between the backup tables in a traditional SQL Server `msdb` database, and the `msdb` database in Azure SQL Managed Instance, such as what information is visible, what tables are supported, and what fields are available. 
+## Overview
 
-## Visible information 
+Backup transparency in SQL Managed Instance is available through the [msdb database](/sql/relational-databases/databases/msdb-database), which makes backup history tables queryable.
 
-The `msdb` database in SQL Managed Instance displays the following backup information: 
+It's important to know about a few key differences between the backup tables in a traditional SQL Server `msdb` database and the `msdb` database in SQL Managed Instance. The main differences include the information that's visible, supported tables, and the fields you can use.
 
-- The type of automated backup taken, such as full, differential, or log.
-- Metadata about native backups taken manually, though some fields, such as file path and usernames, may not be populated. Use the `is_copyonly` column to determine if a backup was taken manually or automatically. 
-- Metadata about the backup such as the status, size, time, and location.
-- The replica where the backup was taken, such as the primary, or secondary. The ability to take backups from the secondary replica is currently in private preview, and only available on the Business Critical service tier. 
+## Included information
 
+The `msdb` database in SQL Managed Instance displays the following backup information:
 
-The `msdb` database **does not** have information about the following: 
+- The type of automated backup taken, such as full, differential, or log.
+- Metadata about native backups taken manually, although fields like file path and usernames might not be populated. Use the `is_copyonly` column to determine whether a backup was taken manually or automatically.
+- Metadata about the backup, including status, size, time, and location.
+- The replica where the backup was taken, such as the primary or secondary managed instance. The ability to take backups from the secondary replica currently is available only on the Business Critical service tier.
 
-- Backups stored for long-term retention, as this is done by copying out files at the storage level, and isn't visible to the instance. 
+The `msdb` database *does not* have the following information:
 
+- Backups that are stored for long-term retention. Backups for long-term retention are made by copying files at the storage level. This type of backup isn't visible to the instance.
 
 ## Supported tables
 
-The `msdb` database in SQL Managed Instance supports the following backup tables: 
+The `msdb` database in SQL Managed Instance supports these backup tables:
 
 - [Backupset](/sql/relational-databases/system-tables/backupset-transact-sql)
 - [Backupmediaset](/sql/relational-databases/system-tables/backupmediaset-transact-sql)
 - [Backupmediafamily](/sql/relational-databases/system-tables/backupmediafamily-transact-sql)
 
-The following backup tables aren't used by SQL Managed Instance, and won't be populated with data: 
+SQL Managed Instance doesn't use the following backup tables, and the tables aren't populated with data:
 
 - [Backupfile](/sql/relational-databases/system-tables/backupfile-transact-sql)
 - [Backupfilegroup](/sql/relational-databases/system-tables/backupfilegroup-transact-sql)
 
-## Removed fields 
+## Removed fields
 
-Since SQL Managed Instance is a cloud service with data stored in storage, the following fields won't be populated with data: 
+Because SQL Managed Instance is a cloud service that stores data in storage, the following fields aren't populated with data:
 
-- Fields that pertain to the user who is logged in. 
-- Fields that pertain to the path of the backup file. 
-- Backup expiration information. 
+- Fields that pertain to the user who is logged in.
+- Fields that pertain to the path of the backup file.
+- Backup expiration information.
 
 ## Considerations
 
-When reviewing your backup history in the `msdb` database, consider the following:
-
-- Backup history doesn't contain all information about user-initiated backups, such as usernames of the user who initiated the backup. 
-- Fields that aren't relevant to the cloud won't be populated, such as the machine name, physical drive, and physical name. 
-- Backup information is inserted to the `msdb` database when the backup completes. Ongoing backups aren't supported. 
+When you review your backup history in the `msdb` database, consider the following information:
 
+- Backup history doesn't contain all information about user-initiated backups, like the username of the user who initiated the backup.
+- Fields that aren't relevant to the cloud aren't populated. Examples include the machine name, the physical drive, and the physical name.
+- Backup information is inserted into the `msdb` database when the backup is finished. Ongoing backups aren't supported.
 
 ## Next steps
 
 - To learn more, review [The msdb database in SQL Server](/sql/relational-databases/databases/msdb-database). 
-- To learn about backups in Azure SQL Managed Instance, review [Automated backups](automated-backups-overview.md)
-- To learn about querying the `msdb` database, review [monitor backup activity](backup-activity-monitor.md)
-
+- To learn about backups in Azure SQL Managed Instance, review [Automated backups](automated-backups-overview.md).
+- To learn about querying the `msdb` database, review [Monitor backup activity](backup-activity-monitor.md).