Merge pull request #26135 from MicrosoftDocs/main

Publish main to live, Tuesday 3:30PM PDT, 07/30

Author: chuckedmonson

microsoft-365/archive/index.yml

@@ -67,7 +67,7 @@ landingContent:
     linkLists:
       - linkListType: overview
         links:
-          - text: Microsoft 365 Backup (Preview)
+          - text: Microsoft 365 Backup
             url: /microsoft-365/backup
           - text: SharePoint Advanced Management
             url: /sharepoint/advanced-management

microsoft-365/backup/TOC.yml

@@ -5,18 +5,16 @@
       href: backup-overview.md
     - name: Admin setup 
       href: backup-setup.md
-    - name: Billing setup
+    - name: Billing & invoice management
       href: backup-billing.md
     - name: Pricing model
       href: backup-pricing.md
-    - name: View and edit policies 
+    - name: Create, view, & edit policies 
       href: backup-view-edit-policies.md
     - name: Restore data 
       href: backup-restore-data.md
     - name: Offboarding
       href: backup-offboarding.md
-    - name: Preview limitations
-      href: backup-limitations.md
     - name: FAQs
       href: backup-faq.md
     - name: Microsoft 365 Backup Storage

microsoft-365/backup/backup-billing.md

@@ -1,26 +1,26 @@
 ---
-title: Set up pay-as-you-go billing for Microsoft 365 Backup (Preview)
+title: Manage billing and invoices for Microsoft 365 Backup
 ms.author: chucked
 author: chuckedmonson
 manager: jtremper
 audience: admin
 ms.reviewer: sreelakshmi
-ms.date: 04/11/2024
+ms.date: 07/31/2024
 ms.topic: conceptual
 ms.service: microsoft-365-backup
 ms.custom: backup
 search.appverid:
 ms.collection:
     - essentials-get-started
 ms.localizationpriority:  medium
-description: Learn how to set up pay-as-you-go billing for Microsoft 365 Backup.
+description: Learn how to set up and manage pay-as-you-go billing and invoices for Microsoft 365 Backup.
 ---
 
-# Set up pay-as-you-go billing for Microsoft 365 Backup (Preview)
+# Manage billing and invoices for Microsoft 365 Backup
 
-As a first step to start using Microsoft 365 Backup, you should link an Azure subscription in Syntex pay-as-you-go, if you haven't already done so. Although Microsoft 365 Backup isn't part of the Microsoft Syntex product suite, this offering is still using the Syntex billing setup for consistency with other Microsoft 365 pay-as-you-go offerings.
+As a first step to start using Microsoft 365 Backup, you should link an Azure subscription in Microsoft Syntex pay-as-you-go, if you haven't already done so. Although Microsoft 365 Backup isn't part of the Microsoft Syntex product suite, this offering is still using the Syntex billing setup for consistency with other Microsoft 365 pay-as-you-go offerings.
 
-## Set up billing
+## Set up pay-as-you-go billing
 
 Use these steps to set up pay-as-you-go billing for Microsoft 365 Backup.
 
@@ -110,7 +110,7 @@ To view tags:
 
         - **servicetype** is OneDrive, SharePoint, or Exchange.
 
-        - **applications** is coming soon.
+        - **applications** shows a list of app IDs.
 
     - Azure cost analysis - filter by tag.
 

microsoft-365/backup/backup-faq.md

@@ -1,11 +1,11 @@
 ---
-title: Frequently asked questions about Microsoft 365 Backup (Preview)
+title: Frequently asked questions about Microsoft 365 Backup
 ms.author: chucked
 author: chuckedmonson
 manager: jtremper
 audience: admin
 ms.reviewer: sreelakshmi
-ms.date: 04/11/2024
+ms.date: 07/31/2024
 ms.topic: conceptual
 ms.service: microsoft-365-backup
 ms.custom: backup
@@ -17,38 +17,36 @@ ms.localizationpriority:  medium
 description: Read frequently asked questions about Microsoft 365 Backup.
 ---
 
-# Frequently asked questions about Microsoft 365 Backup (Preview)
+# Frequently asked questions about Microsoft 365 Backup
 
-> [!NOTE]
-> This feature is currently in preview and subject to change.
 
 #### Has Microsoft's stance on shared responsibility of data protection changed?
 
-No, we still have the same point of view, but are now offering additional tools to help organizations achieve those goals and responsibilities.
+No, we still have the same point of view, but are now offering more tools to help organizations achieve those goals and responsibilities.
 
 #### Why don’t Disaster Recovery copies suffice for my backup?
 
-Disaster Recovery (DR) is the ability to recover from a situation in which the primary data center is unable to continue to operate. A DR copy with Microsoft 365 maintains the current state of content, not any historical versions from prior points in time. Microsoft 365 Backup provides additional benefit by giving you a way to restore data back to a healthy state in the past with fast RTO to with short RPO intervals.
+Disaster Recovery (DR) is the ability to recover from a situation in which the primary data center is unable to continue to operate. A DR copy with Microsoft 365 maintains the current state of content, not any historical versions from prior points in time. Microsoft 365 Backup offers the added advantage of allowing you to restore data to a previous healthy state quickly, with fast RTO (recovery time objectives) and short RPO (recovery point objectives).
 
 #### Why don’t versions already solve this point in time restore problem?
 
-Versions give individual users a way to restore files or sites to prior points in time, but that kind of recovery method doesn't scale well for mass ransomware attacks where an admin needs to orchestrate the recovery. Versions might also be exhausted depending on the version limit set by the admin.
+Versions give individual users a way to restore files or sites to prior points in time, However, that kind of recovery method doesn't scale well for large-scale ransomware attacks where an admin needs to orchestrate the recovery. Versions might also be exhausted depending on the version limit set by the admin.
 
 #### Why don’t legal holds solve the problem of keeping all versions of items for recovery?
 
 Legal holds retain data, but that feature is optimized for export (for example, via eDiscovery), not for mass restore. Microsoft 365 Backup gives the right enhanced restore tooling for ransomware and accidental/malicious deletions at scale, plus optimized performance for those scenarios.
 
-#### What mailbox changes are “backed up”?
+#### What mailbox changes are "backed up"?
 
-Mailbox backup enables the recovery of copies of mailbox item “versions.” Versions are created by two types of actions:
+Mailbox backup enables the recovery of copies of mailbox item "versions." Two types of actions create versions:
 
 - Modifications
 - Deletions
 
 Example events that are versions and recoverable via backup:
 
 **User action**
-- Edit a received email using ‘edit message’ via OL
+- Edit a received email using ‘edit message’ via Outlook
 - Edit a Note (not draft)
 - Remove an attachment from an email
 - Edit an attachment to an email
@@ -71,17 +69,40 @@ Example events that aren't versioned or recoverable via backup:
 
 #### What is the service recovery point objective?
 
-The recovery point objective (RPO) is the maximum amount of time between the most recent backup and a data destruction event. Stated another way, it’s the amount data lost due to a data destruction event not recoverable via the backups. In the case of Microsoft 365 Backup, the RPOs are:
+The recovery point objective (RPO) is the maximum amount of time between the most recent backup and a data destruction event. Stated another way, it’s the amount data lost due to a data destruction event not recoverable via the backups. For Microsoft 365 Backup, the RPOs are:
 
-For OneDrive and SharePoint, the RPO for the first two weeks is 15 minutes, then one week beyond that. This means for the first two weeks, the most amount of data that can be lost due to a data destruction event is roughly 10 minute’s worth of the most recent data. Likewise, after two weeks, the most amount of data that can be lost is a week’s worth of data.
+- For OneDrive and SharePoint, the RPO for the first two weeks is 10 minutes, then one week beyond that. This means for the first two weeks, the most amount of data that can be lost due to a data destruction event is roughly 10 minute’s worth of the most recent data. Likewise, after two weeks, the most amount of data that can be lost is a week’s worth of data.
 
-For Exchange Online, the RPO is 10 minutes, meaning the most amount of data that can be lost due to a data destruction event is roughly 10 minutes’s worth of data.
+- For Exchange Online, the RPO is 10 minutes, meaning the most amount of data that can be lost due to a data destruction event is roughly 10 minutes’s worth of data.
 
 Let's start with what it doesn't mean: We are *not* taking snapshots every 10 minutes.
 
-Backup frequency of 10 minutes (if the item is modified) means that changes to the item will be saved as a version once every 10 minutes, no matter how many changes are made in that 10-minute interval. For example, if a ransomware attack encrypts the email item every minute, will we take six copies in an hour.
-<!---
-Let's start with what it doesn't mean: We are *not* taking snapshots every 10 seconds.
+A backup frequency of 10 minutes (if the item is modified) means that any changes made to the item will be saved as a new version every 10 minutes, regardless of how many changes occur within that 10-minute period. For example, if a ransomware attack encrypts the email item every minute, we'll take six copies in an hour.
+
+#### What happens when user content is backed up but then is removed or deleted from Microsoft Entra ID (formerly Azure Active Directory)?
+
+When a user is removed from the backup policy, the backup of the OneDrive account or Exchange mailbox is retained for one year from the date the backup was created.
 
-Backup frequency of 10 seconds (if the item is modified) means that changes to the item will be saved as a version once every 10 seconds, no matter how many changes are made in that 10-second interval. For example, if a ransomware attack encrypts the email item every second, will we take six copies in a minute.
+When a user is deleted from Microsoft Entra ID, the backup of the OneDrive account or Exchange mailbox is retained for one year from the date the backup was created.
+
+When a site is removed from the backup policy, the backup of the SharePoint site will be held for 52 weeks from the time a given restore point was created for that site.
+
+#### How can I restore the OneDrive account or Exchange mailbox for a user who is deleted from Microsoft Entra ID (formerly Azure Active Directory)?
+
+> [!NOTE]
+> Deleted users will appear as "–" in the user interface because the user does not exist in the tenancy. However, the backups and associated restore points will be retained for the full 365-day retention period from when a given restore point was originally created.
+
+If the user has been deleted within the past 30 days, the best option is to restore the user based on instructions found at [Restore a user in the Microsoft 365 admin center](/microsoft-365/admin/add-users/restore-user). Once the user is reconstituted, the name will reappear in the Backup tool restore experience, and the rest of the experience will work as normal.
+
+For OneDrive, you can restore the OneDrive to the original URL or a new URL. At that time, the OneDrive is in an "orphaned" state. To connect the OneDrive to a user, see [Fix site user ID mismatch in SharePoint or OneDrive](/sharepoint/troubleshoot/sharing-and-permissions/fix-site-user-id-mismatch).
+
+For Exchange, if the user account is currently or permanently deleted, Microsoft 365 Backup retains the inactive mailbox for the duration of the backup policy. To recover and restore the inactive mailbox, see the following guidance:
+
+- [Recover an inactive mailbox](/purview/recover-an-inactive-mailbox)
+- [Restore an inactive mailbox](/purview/restore-an-inactive-mailbox)
+
+Once an inactive mailbox is recovered and restored to a new mailbox, the new mailbox must be added to the backup policy if desired.
+
+<!---
+- For Exchange, a user account will be in a soft-deleted state for 30 days after it's deleted. To restore the user, see [Restore a user in the Microsoft 365 admin center](/microsoft-365/admin/add-users/restore-user). Once you restore the user, you can use the restore feature in Microsoft 365 Backup to restore as usual.
 --->

microsoft-365/backup/backup-offboarding.md

@@ -1,11 +1,11 @@
 ---
-title: Offboarding in Microsoft 365 Backup (Preview)
+title: Offboarding in Microsoft 365 Backup
 ms.author: chucked
 author: chuckedmonson
 manager: jtremper
 audience: admin
 ms.reviewer: sreelakshmi
-ms.date: 04/11/2024
+ms.date: 07/31/2024
 ms.topic: conceptual
 ms.service: microsoft-365-backup
 ms.custom: backup
@@ -16,17 +16,12 @@ ms.localizationpriority:  medium
 description: Learn about how to offboard usage in Microsoft 365 Backup.
 ---
 
-# Offboarding in Microsoft 365 Backup (Preview)
+# Offboarding in Microsoft 365 Backup
 
-> [!NOTE]
-> This feature is currently in preview and subject to change.
-
-To no longer use the Microsoft 365 Backup tool, you must offboard usage. This action includes pausing and deleting all active policies and deleting all of the backed-up data. During the preview, there are three ways that offboarding is initiated:
+To no longer use the Microsoft 365 Backup tool, you must offboard usage. This action includes pausing and deleting all active policies and deleting all of the backed-up data. There are two ways that offboarding is initiated:
 
 - Disable the tool in the pay-as-you-go billing setup panel where you first enabled the tool.
 
-- Call into support to ask Microsoft to offboard you from the tool. If you’d like offboarding to happen faster than default (with a minimum of 30 days), you can do this via the support call.
-
 - If your billing account goes into an unhealthy state.
 
 ## Offboarding recovery undo period
@@ -64,10 +59,12 @@ Retention and deletion policies don't “flow through” to the backups. This me
 
 ### Sensitivity labels
 
-Restoration of any data (such as sites or mailbox items) reverts the sensitivity labels of the data to the state of that protected item at the prior point in time from which it's being restored (that is, the state of labeling at the point in time from which the content is being restored; in other words, the state reverts to the prior point in time).
+Restoration of any data (such as sites or mailbox items) reverts the data's sensitivity labels to the state of that protected item at the prior point from which it's being restored. That is, the state of labeling at the point in time from which the content is being restored; in other words, the state reverts to the prior point in time.
 
+<!---
 ## Backup data deletion and undo grace periods
 
-If you need to delete data from the backups during the preview period, you must offboard from the offering entirely and delete all backups. In the future, we'll enable more granular restore point deletion capabilities.
+If you need to delete data from the backups, you must offboard from the offering entirely and delete all backups. In the future, we'll enable more granular restore point deletion capabilities.
 
 Any offboarding or backup deletion activities trigger a 29-day grace period where we'll hold the backup data. If you re-enable the tool, the backups are present in the tool again.  
+--->