-**PREVIEW FEATURE**: To terminate your Feature Preview during the Preview Period, stop using the Preview Feature. Microsoft may change or discontinue the Preview Feature at any time with or without notice. Microsoft may also choose not to make the Preview Feature generally commercially available.

-During the Preview Period, Company will allow its tenant admins to back up SharePoint sites, OneDrive accounts, and Exchange mailboxes. Company must be aware that this is a preview service and all the limitations described in these Terms and Conditions.

-Microsoft 365 Backup uses pay-as-you-go (PAYG) billing through an Azure subscription. Microsoft 365 Backup billing is determined by how much data in GB you backup using Microsoft 365 Backup in GBs. Company will be able to view this usage as meter events through the Azure subscription it chooses.

-**Effects upon Termination.** Once terminated, Company will no longer have access to Microsoft 365 Backup and all the backed-up content if Microsoft doesn't continue with the then generally available Microsoft 365 Backup features. Should Microsoft choose to make the Microsoft 365 Backup service generally available a pay-as-you-go (PAYG) billing through an Azure subscription, Company may continue without interruption.

-This Agreement can't be extended. Microsoft may also choose not to make the Preview Feature generally commercially available.

-To manage many properties of user account for Skype for Business Online, you must specify them as properties of policies with PowerShell for Microsoft 365.

-

-2. Open a Windows PowerShell command prompt and run the following commands:

-

-

-

-

-

-> A Skype for Business Online dial plan is a policy in every respect except the name. The name "dial plan" was chosen instead of, say, "dialing policy" in order to provide backward compatibility with Office Communications Server and with Exchange.

-> That returns a list of all the voice policies available to you. Keep in mind, however, that not all policies can be assigned to all users. This is due to various restrictions involving licensing and geographic location. (The so-called "[usage location](/previous-versions/azure/dn194136(v=azure.100)).") If you want to know the external access policies and the conferencing policies that can be assigned to a particular user, use commands similar to these:

-The ApplicableTo parameter limits the returned data to policies that can be assigned to the specified user (for example, Alex Darrow). Depending on licensing and usage location restrictions, that might represent a subset of all the available policies.

-In some cases, properties of policies aren't used with Microsoft 365, while others can only be managed by Microsoft support personnel.

-These service advisories are displayed in the Microsoft 365 admin center. To view these service advisories, go to **Health** | **[Service health](https://go.microsoft.com/fwlink/p/?linkid=842900)** | **Exchange Online**. Here's an example of eDiscovery service advisory.

-The Page Diagnostics for SharePoint tool is a browser extension for the new Microsoft Edge (https://www.microsoft.com/edge) and Chrome browsers that analyzes both SharePoint modern portal and classic publishing site pages. The tool provides a report for each analyzed page showing how the page performs against a defined set of performance criteria. To install and learn about the Page Diagnostics for SharePoint tool, visit [Use the Page Diagnostics tool for SharePoint](page-diagnostics-for-spo.md).

->The Page Diagnostics tool only works for SharePoint, and cannot be used on a SharePoint system page.

-[Use the Office 365 Content Delivery Network (CDN) with SharePoint](use-microsoft-365-cdn-with-spo.md)

-| |This column applies to Loop content: <ul><li>Created in all other places that don't have tightly associated collaborative storage (e.g. Teams chat, Outlook email, Word for the web, Whiteboard) ➡️️ in the creator's OneDrive <li>Created in places that have dedicated shared storage (e.g. Teams channels) ➡️️ SharePoint </ul>|This column applies to Loop content: <ul><li>Created inside the Loop app: Workspaces, Ideas ➡️ in SharePoint Embedded, one container per Loop workspace </ul>|

-|Admin toggles |**[Admin Toggles](/microsoft-365/loop/loop-components-configuration#available-policy-settings)** exist to turn on or off creation of and live rendering of Loop components in the Microsoft 365 ecosystem. If you enable Loop components in the Microsoft 365 ecosystem via the primary toggle, there are additional separate toggles to turn on or off Loop components in Outlook or Teams chats and channels. There's also an additional toggle to turn on or off Loop components for collaborative meeting notes. <br><br>Organizations with eCommunication regulations can choose to leave Loop components on across the Microsoft 365 ecosystem while using the independent toggles for communication tools during evaluation of Loop's data lifecycle, governance, and compliance capabilities.|**[Admin Toggle](/microsoft-365/loop/loop-workspaces-configuration)** exists to turn on or off creation of content stored in SharePoint Embedded. This includes controlling creation of Loop Ideas and creation of new workspaces.|

-|Multi-Geo |**[Multi-Geo](/microsoft-365/enterprise/microsoft-365-multi-geo)** capabilities are supported, including creation of .loop files in a user's OneDrive in the geo that matches the user's [preferred data location](/microsoft-365/enterprise/plan-for-multi-geo#best-practices) and ability to move the user's OneDrive when their preferred data location changes.|**[Multi-Geo](/microsoft-365/enterprise/microsoft-365-multi-geo)** capabilities for Loop workspaces are supported using the [same mechanism as SPO sites or OneDrive](/microsoft-365/enterprise/m365-dr-workload-spo#move-a-sharepoint-site-or-sharepoint-embedded-container-site), including rehome. Manage the location of shared Loop workspaces like you would other collaboration artifacts, like SharePoint sites or Teams channels. <br><br>**Not Yet Available**: <br>Loop does not create user-owned workspaces. All workspaces are created as tenant-owned, in the tenant default geo.|

-|User leaves organization |When a user leaves an organization, [OneDrive retention policies](/sharepoint/retention-and-deletion) apply to the .loop files in their OneDrive just as they do to other content created by the user. See [Loop storage](#loop-storage) for more information.|Manage the lifetime of shared Loop workspaces like you would other collaboration artifacts, like SharePoint sites or Teams channels. <br><br>**Not Yet Available**: <br>Loop does not create user-owned workspaces. All workspaces are created as tenant-owned.|

-|Search and Collection |Microsoft **[Purview eDiscovery](/microsoft-365/loop/loop-components-teams#do-loop-and-fluid-files-support-ediscovery)** supports search and collection, review (premium only), and export (premium only) as HTML or original. You can also download and reupload the files to any OneDrive to view them in their native format.|Microsoft **[Purview eDiscovery](/microsoft-365/loop/loop-components-teams#do-loop-and-fluid-files-support-ediscovery)** supports search and collection, review (premium only), and export (premium only) as HTML or original. You can also download and reupload the files to any OneDrive to view them in their native format.|

-|Export |Microsoft **[Graph API](/graph/api/driveitem-get-content-format)** export support.|**Not Yet Available**: <br>[Programmatic API access to Loop workspace containers](#programmatic-apis-not-yet-available) isn't yet available.|

-By reviewing the above information, you can make an informed decision on whether Microsoft Loop is ready for use as a software solution in your organization. As always, we continue to update this and other documentation to provide the compliance status of Microsoft Loop to help you make the best decisions for your organization.

-When you share only a Loop page, you're giving users access to that specific page exclusively (not the whole workspace). The user can choose to use a company share link or people-specific share link; unless their tenant admin disabled some of the share link types. When sharing a page, you can choose to grant the user "*edit*", or "*read only*" access.

-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 user, which will enable the flow to create a guest account for the user.

-If the above conditions are met, then you can share with guest users by:

-Sharing with external participants is done through "Share with specific people" links. Company-wide share links won't work with external participants. You must designate the guest user explicitly in the share dialog.

-When a guest user accesses the Loop workspace, page, or component from the link from your organization, they sign in and access the shared content using their guest account. They'll need to utilize the share link again to access the Loop workspace, page, or component in the future, as the content from your organization won't be accessible via their standard account.

-If you would like to disable guest sharing of Loop workspaces independently of your organization-level OneDrive and SharePoint sharing setting, please see [set sharing capabilities of applications](/sharepoint/dev/embedded/concepts/admin-exp/consuming-tenant-admin/ctapowershell#set-sharing-capability-of-applications) and use Owning App ID: `a187e399-0c36-4b98-8f04-1edc167a0996`.

-Currently, owners can't assign new members as owners. If the owner leaves the company, the workspace becomes ownerless. Administrators can't assign new owners to ownerless workspaces.

-There are other types of groups and membership lists in the Microsoft ecosystem, such as Microsoft 365 groups and Security groups. Currently, Loop workspace membership does not use these groups or lists.

-Shared workspaces are permissioned with a roster and continue to exist even if someone leaves the company. However, if the creator of the workspace is the person who left the company, then others can't delete the workspace.

-Personal workspaces are also permissioned with a roster, but there's only one person in them by design. When a user leaves a company, their personal workspaces become ownerless.

-See [available admin capabilities](/microsoft-365/loop/loop-compliance-summary#available-admin-capabilities) section of the [Summary of governance, lifecycle, and compliance capabilities](/microsoft-365/loop/loop-compliance-summary) for more information.

-The *contracts prbuilt model* analyzes and extracts key information from contract documents. The model recognizes contracts in various formats and extracts key contract information, such as client name and address, contract duration, and renewal date.