From 769a72f4a6ddc9ff0d13a769d771085319f59129 Mon Sep 17 00:00:00 2001 From: Jen Zamora <51343414+jenzamora@users.noreply.github.com> Date: Wed, 8 Jan 2025 15:59:18 -0800 Subject: [PATCH 1/6] Update Loop workspaces storage permissions Restaged updates made in public repo to private repo. --- .../loop/loop-workspaces-storage-permission.md | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/microsoft-365/loop/loop-workspaces-storage-permission.md b/microsoft-365/loop/loop-workspaces-storage-permission.md index 5b3ac9da86c..05368c36b0a 100644 --- a/microsoft-365/loop/loop-workspaces-storage-permission.md +++ b/microsoft-365/loop/loop-workspaces-storage-permission.md @@ -49,6 +49,10 @@ Loop app workspaces are stored inside your tenant, within SharePoint Embedded. A ## Content permissions mechanism +Loop workspaces have a maximum size of 25TB per workspace. This limit can't be increased or decreased. Workspace content counts towards a user's storage quota, and since this per-user storage quota is always less than 25TB, the 25TB limit should never be reached, in practice. Loop workspaces are implemented as SharePoint Embedded containers. Learn more about [SharePoint Embedded container limits](/sharepoint/dev/embedded/concepts/app-concepts/limit-calling). + +## Loop workspace storage limits + Each Loop app workspace uses storage for the workspace in [SharePoint Embedded](/sharepoint/dev/embedded/concepts/admin-exp/consuming-tenant-admin/cta). Additionally, the Loop app creates a roster for that workspace to govern access to the full workspace. When pages are shared from the workspace, we create a sharing link using your company's default sharing link type as configured for OneDrive and SharePoint. Sharing the workspace in Loop adds the user to the workspace roster. All workspace roster members have access and "*editing*" permissions to all the Loop pages in that workspace. @@ -67,7 +71,7 @@ You can share Loop workspaces, pages, and components with users external to your - Your organization must allow sharing files with guests. Learn how to [manage this policy](/sharepoint/turn-external-sharing-on-or-off#change-the-organization-level-external-sharing-setting). - The user you're sharing with must have a guest account in your tenant or [Business-to-Business Invitation Manager is enabled](/entra/external-id/what-is-b2b). -- Your organization doesn't have sensitivity labels configured. Loop external sharing doesn't work for companies with sensitivity labels configured. Once sensitivity labels for Loop workspaces, pages, and components are generally available, then external sharing for companies with sensitivity labels configured does not function. Microsoft Roadmap ID 421614 addresses this. +- Your organization doesn't have sensitivity labels configured. Loop external sharing doesn't work for companies with sensitivity labels configured. Once sensitivity labels for Loop workspaces, pages, and components are generally available, then external sharing for companies with sensitivity labels configured doesn't function. Microsoft Roadmap ID 421614 addresses this. Workspaces can only be shared with users that have an existing guest account in your tenant. If Business-to-business Invitation Manager is enabled, users can share a page or component with a guest, which enables the flow to create a guest account for the user. @@ -85,7 +89,7 @@ When a guest accesses the Loop workspace, page, or component from the link from If you would like to disable guest sharing of Loop workspaces independently of your organization-level OneDrive and SharePoint sharing setting, see [application external sharing override](/sharepoint/dev/embedded/concepts/app-concepts/sharing-and-perm#application-external-sharing-override) and the OwningApplicationID `a187e399-0c36-4b98-8f04-1edc167a0996`. -Unlike SharePoint sites, there is no admin setting to configure guest sharing of specific Loop workspaces. Direct users toward [sensitivity labeling](/purview/sensitivity-labels-loop) for per-workspace external sharing configuration. Admin's can also [configure sensitivity labels](/sharepoint/dev/embedded/concepts/security-and-compliance#security-features) on containers. +Unlike SharePoint sites, there's no admin setting to configure guest sharing of specific Loop workspaces. Direct users toward [sensitivity labeling](/purview/sensitivity-labels-loop) for per-workspace external sharing configuration. Admin's can also [configure sensitivity labels](/sharepoint/dev/embedded/concepts/security-and-compliance#security-features) on containers. ## Loop workspace membership and Microsoft 365 groups @@ -106,7 +110,7 @@ The Loop app is designed for both shared and personal workspaces. #### Shared Workspaces - Shared workspaces are permissioned with a roster. If the owner leaves the company, the workspace becomes ownerless, remains in the tenant, and isn't automatically deleted. -- If the creator of the workspace is the person who left the company, others cannot delete the workspace. +- If the creator of the workspace is the person who left the company, others can't delete the workspace. #### Personal Workspaces @@ -116,20 +120,20 @@ The Loop app is designed for both shared and personal workspaces. ##### Ideas - Ideas is a tenant-owned personal workspace, permissioned with a roster but designed for single-person use. -- When a user leaves the company, like a shared workspace, their Ideas workspace becomes ownerless, remains in the tenant, and is not automatically deleted. +- When a user leaves the company, like a shared workspace, their Ideas workspace becomes ownerless, remains in the tenant, and isn't automatically deleted. ##### Copilot Pages - Copilot Pages is a user-owned workspace, created only by Copilot, and is lifecycle managed with the user account. - Copilot Pages is deleted when the user account is deleted from the organization. -- User-owned workspaces cannot be permanently reassigned to a new owner. These workspaces follow the same cleanup schedule as OneDrive: 30 days active, then soft deleted, and permanently purged 93 days after soft deletion. +- User-owned workspaces can't be permanently reassigned to a new owner. These workspaces follow the same cleanup schedule as OneDrive: 30 days active, then soft deleted, and permanently purged 93 days after soft deletion. - Admins can recover content during the soft delete period using the SharePoint Admin Center or PowerShell. -Note: A feature for IT admins to assign additional temporary custodians during the cleanup period of user-owned workspaces to make copies of content is not yet available. Microsoft Roadmap ID 421612 addresses this. +Note: A feature for IT admins to assign additional temporary custodians during the cleanup period of user-owned workspaces to make copies of content isn't yet available. Microsoft Roadmap ID 421612 addresses this. ### In Loop components created in Microsoft 365 outside of the Loop app -Loop components created outside of Loop are stored in the OneDrive of the person who created the component, or if created in a place with shared storage like a Teams channel, they are stored in the SharePoint folder for that channel. When stored in OneDrive, if that user leaves the organization, the standard OneDrive IT policy is applied. When stored in SharePoint, the standard SharePoint IT policy is applied. +Loop components created outside of Loop are stored in the OneDrive of the person who created the component, or if created in a place with shared storage like a Teams channel, they're stored in the SharePoint folder for that channel. When stored in OneDrive, if that user leaves the organization, the standard OneDrive IT policy is applied. When stored in SharePoint, the standard SharePoint IT policy is applied. ## Management of Loop content From 3ca71d272e065f8e4f2434c7a62e319e2926fd19 Mon Sep 17 00:00:00 2001 From: Jen Zamora <51343414+jenzamora@users.noreply.github.com> Date: Wed, 8 Jan 2025 16:05:48 -0800 Subject: [PATCH 2/6] Update loop-workspaces-storage-permission.md Restaged updates to private repo (accidentally made in public repo). --- microsoft-365/loop/loop-workspaces-storage-permission.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/microsoft-365/loop/loop-workspaces-storage-permission.md b/microsoft-365/loop/loop-workspaces-storage-permission.md index 05368c36b0a..e24cd6724ec 100644 --- a/microsoft-365/loop/loop-workspaces-storage-permission.md +++ b/microsoft-365/loop/loop-workspaces-storage-permission.md @@ -47,11 +47,11 @@ Where the Loop content was originally created determines its storage location: Loop app workspaces are stored inside your tenant, within SharePoint Embedded. All Loop workspaces and pages, including Shared workspaces, Personal workspaces, Ideas, and Copilot Pages, count against your tenant's storage quota, starting November 2023. -## Content permissions mechanism +## Loop workspace storage limits Loop workspaces have a maximum size of 25TB per workspace. This limit can't be increased or decreased. Workspace content counts towards a user's storage quota, and since this per-user storage quota is always less than 25TB, the 25TB limit should never be reached, in practice. Loop workspaces are implemented as SharePoint Embedded containers. Learn more about [SharePoint Embedded container limits](/sharepoint/dev/embedded/concepts/app-concepts/limit-calling). -## Loop workspace storage limits +## Content permissions mechanism Each Loop app workspace uses storage for the workspace in [SharePoint Embedded](/sharepoint/dev/embedded/concepts/admin-exp/consuming-tenant-admin/cta). Additionally, the Loop app creates a roster for that workspace to govern access to the full workspace. When pages are shared from the workspace, we create a sharing link using your company's default sharing link type as configured for OneDrive and SharePoint. From 5d263d95c5f8b74d01473dec89b0d64ff056fa07 Mon Sep 17 00:00:00 2001 From: Jen Zamora <51343414+jenzamora@users.noreply.github.com> Date: Wed, 8 Jan 2025 16:18:03 -0800 Subject: [PATCH 3/6] Update date and fix link typo --- microsoft-365/loop/loop-workspaces-storage-permission.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/microsoft-365/loop/loop-workspaces-storage-permission.md b/microsoft-365/loop/loop-workspaces-storage-permission.md index e24cd6724ec..ea7c7b8043f 100644 --- a/microsoft-365/loop/loop-workspaces-storage-permission.md +++ b/microsoft-365/loop/loop-workspaces-storage-permission.md @@ -7,7 +7,7 @@ audience: Admin ms.topic: conceptual ms.service: loop ms.reviewer: michalbr -ms.date: 06/26/2024 +ms.date: 01/08/2025 ms.localizationpriority: medium search.appverid: MET150 ms.collection: @@ -49,7 +49,7 @@ Loop app workspaces are stored inside your tenant, within SharePoint Embedded. A ## Loop workspace storage limits -Loop workspaces have a maximum size of 25TB per workspace. This limit can't be increased or decreased. Workspace content counts towards a user's storage quota, and since this per-user storage quota is always less than 25TB, the 25TB limit should never be reached, in practice. Loop workspaces are implemented as SharePoint Embedded containers. Learn more about [SharePoint Embedded container limits](/sharepoint/dev/embedded/concepts/app-concepts/limit-calling). +Loop workspaces have a maximum size of 25TB per workspace. This limit can't be increased or decreased. Workspace content counts towards a user's storage quota, and since this per-user storage quota is always less than 25TB, the 25TB limit should never be reached, in practice. Loop workspaces are implemented as SharePoint Embedded containers. Learn more about [SharePoint Embedded container limits](/sharepoint/dev/embedded/concepts/app-concepts/limits-calling). ## Content permissions mechanism From b7ced7f2f8e8e27f4833e2e8e599cc7d6218360d Mon Sep 17 00:00:00 2001 From: Ruchika Mittal Date: Thu, 9 Jan 2025 06:25:55 +0530 Subject: [PATCH 4/6] note formatting --- microsoft-365/loop/loop-workspaces-storage-permission.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/microsoft-365/loop/loop-workspaces-storage-permission.md b/microsoft-365/loop/loop-workspaces-storage-permission.md index ea7c7b8043f..7b6069f85bc 100644 --- a/microsoft-365/loop/loop-workspaces-storage-permission.md +++ b/microsoft-365/loop/loop-workspaces-storage-permission.md @@ -129,7 +129,8 @@ The Loop app is designed for both shared and personal workspaces. - User-owned workspaces can't be permanently reassigned to a new owner. These workspaces follow the same cleanup schedule as OneDrive: 30 days active, then soft deleted, and permanently purged 93 days after soft deletion. - Admins can recover content during the soft delete period using the SharePoint Admin Center or PowerShell. -Note: A feature for IT admins to assign additional temporary custodians during the cleanup period of user-owned workspaces to make copies of content isn't yet available. Microsoft Roadmap ID 421612 addresses this. +> [!NOTE] +> A feature for IT admins to assign additional temporary custodians during the cleanup period of user-owned workspaces to make copies of content isn't yet available. Microsoft Roadmap ID 421612 addresses this. ### In Loop components created in Microsoft 365 outside of the Loop app From 64e4bdeee3763cc5faaf57cc3d4beda3c464ca48 Mon Sep 17 00:00:00 2001 From: e sung Date: Wed, 8 Jan 2025 16:59:11 -0800 Subject: [PATCH 5/6] Add one more note on archive mailboxes being included --- microsoft-365/backup/backup-view-edit-policies.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/microsoft-365/backup/backup-view-edit-policies.md b/microsoft-365/backup/backup-view-edit-policies.md index ab8459c750a..b21b63752e4 100644 --- a/microsoft-365/backup/backup-view-edit-policies.md +++ b/microsoft-365/backup/backup-view-edit-policies.md @@ -138,6 +138,9 @@ Follow these steps to set up a backup policy for Exchange mailboxes sites using 6. On the **Choose selection method** page, you can set up shared or user mailboxes using any or all three ways. Other Exchange recipient types, such as room mailboxes, are not supported at this time. A protection scope is the scope of mailboxes within Exchange that you want to protect with Microsoft 365 Backup. + > [!NOTE] + > Adding a mailbox to the backup policy will back up the primary and archive mailboxes. + ![Screenshot of the Choose selection method page for Exchange.](../media/m365-backup/backup-choose-selection-method-exchange.png) a. Under **Upload a list of mailboxes in a CSV file**, you can upload a list of accounts to back up via a CSV file. From 8bb67d4764890d784d520da1c1bcceb14cce523d Mon Sep 17 00:00:00 2001 From: Chuck Edmonson <33042436+chuckedmonson@users.noreply.github.com> Date: Wed, 8 Jan 2025 17:11:37 -0800 Subject: [PATCH 6/6] Update backup-restore-data.md --- microsoft-365/backup/backup-restore-data.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/microsoft-365/backup/backup-restore-data.md b/microsoft-365/backup/backup-restore-data.md index cf31089b247..6c1b909758a 100644 --- a/microsoft-365/backup/backup-restore-data.md +++ b/microsoft-365/backup/backup-restore-data.md @@ -5,7 +5,7 @@ author: chuckedmonson manager: jtremper audience: admin ms.reviewer: sreelakshmi -ms.date: 10/25/2024 +ms.date: 01/09/2025 ms.topic: conceptual ms.service: microsoft-365-backup ms.custom: backup @@ -239,8 +239,6 @@ Microsoft 365 Backup supports the backup and restoration of any site and user ac - For restores to a new URL, it might take up to 15 minutes for the destination URL to be displayed in the tool once a SharePoint site or OneDrive account restore to a new URL session completes. -- For restores to a new URL, only the admin who executed the restore has ownership permissions for the restored SharePoint sites or OneDrive accounts in the new URLs. Restores to the same URL reverts permissions to their original state. - - A OneDrive account or SharePoint site that is under the strict SEC 17a-4(f) hold policy will fail any in-place restores so as to honor that immutability promise. For sites under that type of hold, you have to restore to a new URL or remove the hold. Any other type of preservation hold that doesn't have a strict admin lockout will allow an in-place restore. Restoring these types of sites as the preservation hold library will be reverted to the prior point in time. A new URL restore is recommended for that type of site as the cleanest option. - The restore point frequency dictates the points in time from which you can recover a prior state of your data. Restore points start being generated when you enable the backup policy for a given OneDrive account, SharePoint Site, or Exchange Online mailbox. For Exchange Online, restore points are available for 10 minutes for the entire year. For OneDrive and SharePoint, the available restore points drop to weekly from 10 minutes for the first two weeks. Based on the defined and currently invariable backup frequency setting previously described, the following example highlights what is possible.