Formatting updates to the SharePoint Embedded side

Author: VesaJuvonen

docs/embedded/concepts/admin-exp/billing.md

@@ -1,15 +1,15 @@
 ---
 title: PAYG billing for SharePoint Embedded
 description: This article explains how to set up PAYG billing
-ms.date: 11/28/2023
+ms.date: 04/09/2024
 ms.localizationpriority: high
 ---
 
 # SharePoint Embedded  Billing experience
 
-This document outlines the steps an admin will have to follow to set up billing, evaluate actual and forecast costs, and pay invoices on SharePoint Embedded.
+This document outlines the steps an admin has to follow to set up billing, evaluate actual and forecast costs, and pay invoices on SharePoint Embedded.
 
-SharePoint Embedded  will be a consumption based Pay-as-you-go (PAYG) offering from SharePoint Online, which means you'll pay only for what you use. As a Developer admin for SharePoint Embedded, you'll set up billing on a container type using SharePoint Online Management Shell and manage forecast of actual costs and invoices in Microsoft Azure portal.
+SharePoint Embedded  will be a consumption based Pay-as-you-go (PAYG) offering from SharePoint Online, which means you pay only for what you use. As a Developer admin for SharePoint Embedded, you set up billing on a container type using SharePoint Online Management Shell and manage forecast of actual costs and invoices in Microsoft Azure portal.
 
 ![Billing pay-as-you-go.](../../images/billing-manage.png)
 
@@ -23,8 +23,8 @@ To enable PAYG on SharePoint Embedded, you need:
 
 ## Roles and Permissions
 
-- Admin who will set up billing relationship for SharePoint Embedded  will need to have owner or contributor permissions on Azure subscription.
-- Admin will need to have a SharePoint Embedded Administrator role to operate billing cmdlets.
+- Admin who sets up billing relationship for SharePoint Embedded need to have owner or contributor permissions on Azure subscription.
+- Admin needs to have a SharePoint Embedded Administrator role to operate billing cmdlets.
 
 ## Steps to establish billing
 

docs/embedded/concepts/admin-exp/cta.md

@@ -1,7 +1,7 @@
 ---
 title: Consuming Tenant Admin
 description: This article describes the role and responsibilities of Consuming Tenant Admin in SharePoint Embedded.
-ms.date: 11/28/2023
+ms.date: 04/09/2024
 ms.localizationpriority: high
 ---
 
@@ -16,11 +16,11 @@ ms.localizationpriority: high
 
 The organizations that use the SharePoint Embedded applications on their Microsoft 365(Microsoft 365) tenants are the consuming tenants and the persona that is responsible for managing these applications on their Microsoft 365 tenancy is the consuming tenant administrator. Consuming tenant administrators can perform various administrative actions on the SharePoint Embedded applications registered on their Microsoft 365 tenant and on the Containers that hold the content. They can also manage tenant level configurations and ensure that data is stored in a secure, protected way that meets customers’ business and compliance policies. In this article, we describe the enterprise manageability features that are supported and can be performed by the consuming tenant administrator.
 
-## 1. Consuming Tenant Admin Role
+## Consuming Tenant Admin Role
 
-Microsoft 365 SharePoint Embedded Administrator serves as the consuming tenant admin.  Global Administrators in Microsoft 365 can assign users the SharePoint Embedded Administrator. The Global Administrator role already has all the permissions of the SharePoint Embedded Administrator role. A SharePoint Administrator can assign themselves the SharePoint Embedded Administrator role to act as a Consuming Tenant Admin for SharePoint Embedded. The SharePoint Embedded Role is available in Microsoft Entra and M365 Admin Center.
+Microsoft 365 SharePoint Embedded Administrator serves as the consuming tenant admin.  Global Administrators in Microsoft 365 can assign users the SharePoint Embedded Administrator. The Global Administrator role already has all the permissions of the SharePoint Embedded Administrator role. A SharePoint Administrator can assign themselves the SharePoint Embedded Administrator role to act as a Consuming Tenant Admin for SharePoint Embedded. The SharePoint Embedded Role is available in Microsoft Entra and Microsoft 365 Admin Center.
 
-## 2. Administration Tools
+## Administration Tools
 
 Consuming tenant admins are able to manage SharePoint Embedded applications with PowerShell commands using [SharePoint Online Management Shell](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online).
 
@@ -29,7 +29,7 @@ To get started using PowerShell to manage SharePoint Embedded, you have to insta
 > [!IMPORTANT]
 > You need version 16.0.24211.12000 or higher to run the commands for SharePoint Embedded.
 
-## 3. Application Administration
+## Application Administration
 
 With PowerShell cmdlets, tenant admin can get a list of SharePoint Embedded applications registered in their Microsoft 365 tenancy. They can also view all the applications that have "read" and/or "write" access and the level of access to these SharePoint Embedded applications.
 
@@ -49,7 +49,7 @@ Get-SPOApplication -OwningApplicationId <OwningApplicationId> -ApplicationId <Ap
 
 OwningApplicationId is the ID of the SharePoint Embedded application and ApplicationId is the ID of the application that has access to the SharePoint Embedded application. Application Administration cmdlets aren't applicable for Microsoft Loop. For more information about using this command, see [Get-SPOApplication cmdlet](/powershell/module/sharepoint-online/get-spoapplication).
 
-## 4. Container Administration
+## Container Administration
 
 ### View Containers
 
@@ -85,7 +85,7 @@ Therefore, it's essential to carefully consider the consequences of deleting a c
 
 When admins delete a Container, it goes into the Recycle Bin. A deleted container can be restored from the Recycle Bin within 93 days. If a container is deleted from the Recycle Bin, or it exceeds the 93-day retention period, it's permanently deleted. Deleting a container deletes everything within it, including all documents and files.
 
-Admins should notify the Container owners before they delete a Container so they can move their data to another ___location, and also inform users when the Container will be deleted.
+Admins should notify the Container owners before they delete a Container so they can move their data to another ___location, and also inform users when the Container is deleted.
 
 > [!WARNING]
 > Deleting a container may cause unexpected issues for the SharePoint Embedded application the Container belongs to and may interrupt usage of the application.
@@ -94,7 +94,7 @@ Admins should notify the Container owners before they delete a Container so they
 Remove-SPOContainer -Identity <ContainerId>
 ```
 
-The `ContainerId` is the ID of the container that will be moved to the deleted container collection. For more information about using this command, see [Remove-SPOContainer cmdlet](/powershell/module/sharepoint-online/remove-spocontainer).
+The `ContainerId` is the ID of the container that is moved to the deleted container collection. For more information about using this command, see [Remove-SPOContainer cmdlet](/powershell/module/sharepoint-online/remove-spocontainer).
 
 ### View deleted containers
 
@@ -121,6 +121,6 @@ Remove-SPODeletedContainer -Identity <ContainerId>
 ```
 
 
-## 5. Security and Compliance Administration
+## Security and Compliance Administration
 
 SharePoint Embedded uses Microsoft’s comprehensive compliance and data governance solutions to help organizations manage risks, protect, and govern sensitive data, and respond to regulatory requirements. Security and compliance solutions work in a similar manner in the SharePoint Embedded platform as they do today in Microsoft 365 platform so that data is stored in a secure, protected way that meets customers’ business and compliance policies while making it easy for Compliance and SharePoint Administrators to enforce critical security and compliance policies on the content. For information on supported security and compliance capabilities, see [Security and Compliance](../security-and-compliance.md).

docs/embedded/concepts/admin-exp/dev-admin.md

@@ -1,7 +1,7 @@
 ---
 title: Developer Admin
-description: This article describes the role and responsibilities of Developer Tenant Admin in SharePoint Embedded
-ms.date: 11/28/2023
+description: This article describes the role and responsibilities of Developer Tenant Admin in SharePoint Embedded.
+ms.date: 04/09/2024
 ms.localizationpriority: high
 ---
 # Developer Admin
@@ -16,11 +16,11 @@ A Microsoft 365 SharePoint Embedded Administrator serves as the developer admin.
 
 ### Billing responsibilities of Developer admin
 
-The developer admin will need to establish billing for SharePoint Embedded while creating container types given they have owner or contributor permissions on the Azure subscription that they use to establish the billing relationship on the product. To learn more about how to set up billing and manage cost and invoice, read about PAYG for [SharePoint Embedded.](./billing.md).
+The developer admin need to establish billing for SharePoint Embedded while creating container types given they have owner or contributor permissions on the Azure subscription that they use to establish the billing relationship on the product. To learn more about how to set up billing and manage cost and invoice, read about PAYG for [SharePoint Embedded.](./billing.md).
 
 ## Administration Tools
 
-Developer admins will be able to manage SharePoint Embedded applications with PowerShell commands using SharePoint Online Management Shell.
+Developer admins are able to manage SharePoint Embedded applications with PowerShell commands using SharePoint Online Management Shell.
 
 To get started using PowerShell to manage SharePoint Embedded, you have to install the SharePoint Online Management Shell and connect to SharePoint Online.
 
@@ -33,6 +33,7 @@ To get started using PowerShell to manage SharePoint Embedded, you have to insta
 > Global Administrators can continue to execute SharePoint Embedded container cmdlets.
 > 
 > If you are a SharePoint Administrator, grant yourself the SharePoint Embedded Admin role as well to execute these cmdlets.
+
 ## PowerShell cmdlets for admin experience
 
 ### Creation of container types
@@ -84,8 +85,6 @@ For more information about billing, see [Billing](./billing.md).
 
 ## Roles and Permissions
 
-The user or admin who will set up billing relationship for SharePoint Embedded will need to have owner or contributor permissions on a Azure subscription.
-
-If you don't have an Azure subscription, follow steps here to [create a subscription](/azure/cloud-adoption-framework/ready/azure-best-practices/initial-subscriptions)
-
+The user or admin who will set up billing relationship for SharePoint Embedded need to have owner or contributor permissions on an Azure subscription.
 
+If you don't have an Azure subscription, follow steps here to [create a subscription.](/azure/cloud-adoption-framework/ready/azure-best-practices/initial-subscriptions)

docs/embedded/concepts/app-concepts/containertypes.md

@@ -1,7 +1,7 @@
 ---
 title: SharePoint Embedded Container Types
 description: This article explains how Container Types work.
-ms.date: 03/05/2023
+ms.date: 04/09/2024
 ms.localizationpriority: high
 ---
 
@@ -16,21 +16,20 @@ There are two kinds of Container Types that a developer tenant can create:
 1. [Trial Container Types](#trial-container-types)
 1. [Standard Container Types](#standard-container-types)
 
-
-
 ## Trial Container Types
 
 To enable customers to explore the development of SharePoint Embedded applications and assess its features, we offer the ability to create a Trial Container Type. Each customer can have only one Trial Container Type in their tenant at a time. The tenant developing the application can utilize Trial Container Types, which aren't linked to a billing profile. In this scenario, the partner tenant remains the same as the consuming tenant. The Trial Container Type remains valid for up to 30 days but can be removed at any time within this period. There are two ways to create a Trial Container Type:
 
 - You can use [SharePoint Embedded Visual Studio Code Extension](../../getting-started/spembedded-for-vscode.md) to create a Trial Container Type in just a few steps. The Visual Studio Code extension also registers your Container Type and creates Containers for you.
-- A Trial Container Type can be created using SharePoint PowerShell. You must be a SharePoint Embedded Administrator or Global Administrator to run this cmdlet. If you are a SharePoint Administrator, grant yourself the SharePoint Embedded Admin role as well to execute these cmdlets.
+- A Trial Container Type can be created using SharePoint PowerShell. You must be a SharePoint Embedded Administrator or Global Administrator to run this cmdlet. If you're a SharePoint Administrator, grant yourself the SharePoint Embedded Admin role as well to execute these cmdlets.
 
 ```powershell
 New-SPOContainerType
 [–TrialContainerType]
 [ -ContainerTypeName <ContainerTypeName>]
 [ -OwningApplicationId <OwningApplicationId>]
 ```
+
 After a Trial Container Type is created, customers can create up to five active Containers in the trial Container Type. Trial Containers are provided with 1 GB of storage space. The Trial Container Type expires after 30 days, resulting in the loss of access to all Containers created using that Container Type. Customers can create a new Trial Container Type, but doing so requires the deletion of ALL existing Trial Containers.
 
 > [!NOTE]
@@ -41,22 +40,21 @@ After a Trial Container Type is created, customers can create up to five active
 ## Standard Container Types
 
 Standard Container Types are associated with a billing profile in [Azure portal](https://portal.azure.com) when they're created. The billing profile includes an Azure Subscription ID and a Region Group. There are two prerequisites to creating s Standard Container:
+
 - An Azure subscription and Resource Group must be present in the [Azure portal](https://portal.azure.com)
 - An App registration must be created in [Microsoft Entra ID](https://entra.microsoft.com)
 
 ## Create a Standard ContainerType
 
 A developer admin can create a new billable Container Type using the following PowerShell cmdlet. Tenants can create a maximum of five Container Types. Trial Container Types don't count against the maximum number of Container Types that a Partner tenant can create.
 
-
 > [!IMPORTANT]
 > Assign the SharePoint Embedded Administrator role available in M365 Admin Center or Microsoft Entra to execute SharePoint Embedded Container commandlets mentioned in this article.
 > 
 > Global Administrators can continue to execute SharePoint Embedded container cmdlets.
 > 
 > If you are a SharePoint Administrator, grant yourself the SharePoint Embedded Admin role as well to execute these cmdlets.
 
-
 > [!NOTE]
 > The user or admin who will set up billing relationship for SharePoint Embedded will need to have owner or contributor permissions on the Azure subscription.
 
@@ -100,4 +98,4 @@ Developer Admins can only delete Trial Container Types and not Standard Containe
 ```powershell
 Remove-SPOContainerType
 [-ContainerTypeId <ContainerTypeId>]
-```
+```

docs/embedded/concepts/security-and-compliance.md

@@ -1,7 +1,7 @@
 ---
 title: Security and Compliance
 description: Details Security and Compliance methods provided by SharePoint Embedded
-ms.date: 11/28/2023
+ms.date: 04/09/2024
 ms.localizationpriority: high
 ---
 
@@ -64,7 +64,7 @@ To limit the eDiscovery Search to one/few SharePoint Embedded Containers, Admins
 
 SharePoint Embedded supports retention and holds policies on content stored in its applications using the Microsoft Purview compliance portal. For more information on DLM, see [Learn about Microsoft Purview Data Lifecycle Management](/purview/data-lifecycle-management).
 
-The existing retention policy will automatically apply to all SharePoint Embedded Containers if the policy is configured for ‘All sites’. Similarly, creating a new retention/hold policy on *All* SharePoint Sites workload will automatically enforce the policy on all SharePoint Online Sites and all Containers within SharePoint Embedded.
+The existing retention policy is applied to all SharePoint Embedded Containers if the policy is configured for ‘All sites’. Similarly, creating a new retention/hold policy on *All* SharePoint Sites workload will automatically enforce the policy on all SharePoint Online Sites and all Containers within SharePoint Embedded.
 
 ![retention policy](../images/sc4.png)
 
@@ -86,7 +86,7 @@ Admins can also restrict the enforcement of a DLP policy to specific SharePoint
 
 ![Configure DLP Policy](../images/sc7.png)
 
-Several scenarios supported by DLP today need user interaction that isn’t natively supported by SharePoint Embedded. For instance, based on its configuration, a DLP policy that prevents external sharing might allow end users to provide a business justification to override the policy. The client app that renders this DLP-flagged file item will need to support such user interactions.
+Several scenarios supported by DLP today need user interaction that isn’t natively supported by SharePoint Embedded. For instance, based on its configuration, a DLP policy that prevents external sharing might allow end users to provide a business justification to override the policy. The client app that renders this DLP-flagged file item needs to support such user interactions.
 
 Policy tips are shown today for files hosted in SharePoint Online so that users are kept informed about DLP-flagged file items and corresponding restrictions. Similarly, for policy tips to be displayed for files hosted in SharePoint Embedded, the client app can choose to provide more support by utilizing the existing Graph APIs for this purpose.