Update overview.md

docs/embedded/administration/consuming-tenant-admin/cta.md

@@ -32,19 +32,23 @@ On PowerShell, the SharePoint Embedded Admin can run the following cmdlets:
 1. Enumerate applications in a tenant
 1. Enumerate containers of an application in a tenant
 1. Enumerate containers of an application sorted basis storage
+1. Enumerate archived containers of an application
+
 1. Edit the sensitivity label on a container
 1. Set sharing capability configuration on a container
 
 For information on consuming tenant admin in [PowerShell](../consuming-tenant-admin/ctapowershell.md)
 
 ### SharePoint Administrator Center
 
-The SharePoint Embedded Admin can access the Active and Deleted containers page on SPAC and perform SharePoint Embedded application level and container level actions. This includes the following:
+The SharePoint Embedded Admin can access the Active, Archived and Deleted containers pages on SPAC and perform SharePoint Embedded application level and container level actions. This includes the following:
 
 1. View the Active container page
+1. View the Archived container page
+
 1. View the Deleted container page
 1. View the detailed information of a container
-1. Soft delete, restore, and purge deleted containers
+1. Archive, soft delete, reactivate, restore, and purge deleted containers
 
 For information on consuming tenant admin in SharePoint Admin see [container management](ctaUX.md)
 
@@ -58,13 +62,14 @@ To use Pass-through SharePoint Embedded App, SharePoint Embedded Admin needs to
 
 ### [Meters](../billing/meters.md)
 
-SharePoint Embedded employs a pay-as-you-go (PAYG) billing model through an Azure subscription. Billing is determined by how much data in GB you store in SharePoint Embedded, transactions used to access and modify the container and container contents, and data that is egressed from the SharePoint Embedded platform. Each of these factors contributes to the overall cost, ensuring that you only pay for the resources and services you use. You can view this usage and billing details in the [Azure Cost Management](https://ms.portal.azure.com/).
+SharePoint Embedded employs a pay-as-you-go (PAYG) billing model through an Azure subscription. Billing is determined by how much data in GB you store in SharePoint Embedded in active and archived states, transactions used to access and modify the container and container contents, and data that is egressed from the SharePoint Embedded platform. Each of these factors contributes to the overall cost, ensuring that you only pay for the resources and services you use. You can view this usage and billing details in the [Azure Cost Management](https://ms.portal.azure.com/).
 
-SharePoint Embedded has three billing meters as shown. Refer to the [product page](https://adoption.microsoft.com/en-us/sharepoint/embedded/) for pricing details 
+SharePoint Embedded has four billing meters as shown. Refer to the [product page](https://adoption.microsoft.com/en-us/sharepoint/embedded/) for pricing details 
 
 | SharePoint Embedded Service Meters |   Meter Unit   |
 | :--------------------------------: | :------------: |
 |              Storage               |      $/GB      |
+|          Archived Storage          |      $/GB      |
 |          API Transactions          | $/Transactions |
 |               Egress               |      $/GB      |
 

docs/embedded/administration/consuming-tenant-admin/ctapowershell.md

@@ -23,8 +23,11 @@ The following are some of the container-specific command actions currently suppo
 
 ### Container administration
 
-- Get details of all containers of a particular SharePoint Embedded application in the tenant
+- Get details of all active containers of a particular SharePoint Embedded application in the tenant
+
 - Get details of a specific container
+- Get details of all archived containers of a particular SharePoint Embedded application in the tenant
+
 - Set the Sensitivity label of a specific container
 - Soft delete a container
 - Get details of all soft deleted containers
@@ -91,6 +94,12 @@ Get-SPOContainer -OwningApplicationId <OwningApplicationId> | FT
 
 The `OwningApplicationId` is the ID of the SharePoint Embedded application. For more information about using this command, see [Get-SPOContainer cmdlet](/powershell/module/sharepoint-online/get-spocontainer). 
 
+Similarly, this command lists all the archived containers within the application with Id OwningApplicationId:
+
+```powershell
+Get-SPOContainer -OwningApplicationId <OwningApplicationId> -ArchiveStatus Archived | FT
+```
+
 > [!NOTE]
 > To enumerate Microsoft Loop containers, use Owning App ID: **a187e399-0c36-4b98-8f04-1edc167a0996** for all the cmdlets of container administration.
 
@@ -173,6 +182,8 @@ Admins can restore a deleted container from the deleted container collection usi
 Restore-SPODeletedContainer -Identity <ContainerId>
 ```
 
+If the container was in archived state at the time of deletion, it gets restored to archived state again.
+
 ### Permanently delete containers
 
 Admins can permanently delete a container from the deleted container collection if the container has no further retention policies applied to it. For more information about using this command, see [Remove-SPODeletedContainer cmdlet](/powershell/module/sharepoint-online/remove-spodeletedcontainer).

docs/embedded/administration/developer-admin/dev-admin.md

@@ -103,6 +103,8 @@ The developer administrator can change container type configuration settings usi
 1. Discoverability Disabled: Controls if file items inside the container surface in other Microsoft 365 properties (MRU, etc.).
 1. Sharing Restricted: Only manager and owner can share files in the container if restricted sharing is true.
 
+1. Archived Enabled: If set to true, the application can support archival of containers. Default value is false.
+
 The following commands can be used to change the configuration settings of SharePoint Embedded applications created on the developer admin’s tenant:
 
 ```powershell

docs/embedded/development/content-experiences/office-experience.md

@@ -13,6 +13,8 @@ Office file experiences for SharePoint Embedded platform will work in a similar
 
 Office documents from SharePoint Embedded apps can be opened for viewing and editing in Office web or in the Office application for a richer viewing and editing experience. AutoSave feature saves your files automatically as your user's work and is enabled for each Word, Excel, and PowerPoint file stored in your SharePoint Embedded Application Apps.
 
+Documents stored in an archived container can’t be viewed or accessed. Applications must handle the archived state of the container by displaying an appropriate error message and guiding end users on the next steps to regain access, such as reactivating the container.
+
 ## View or restore a previous version of an Office document from SharePoint Embedded
 
 Versioning is automatically enabled on each Word, Excel, and PowerPoint file stored in your SharePoint Embedded Apps, that helps your users to see what changes have been made in a file, compare different versions, or restore the version you want. This is incredibly important to your users if a mistake was made, a previous version is preferred, or in multi-user coauthoring scenarios when your users are collaborating with others and someone makes changes your users didn't want in a file.

docs/embedded/getting-started/containertypes.md

@@ -170,6 +170,7 @@ Developer admins can configure selected settings for SharePoint Embedded contain
 | **CopilotEmbeddedChatHosts** | Adds host URLs that are permitted to use the SharePoint Embedded application’s declarative agent experience. | 
 | **DiscoverabilityDisabled**  | Determines whether content from a SharePoint Embedded application is visible across Microsoft 365 experiences. | 
 | **SharingRestricted** | Configures sharing permissions for SharePoint Embedded containers by using role-based access. Supports both open and restrictive sharing models. When restrictive sharing is set to true, only managers and owners can share files in the container.| 
+| **IsArchiveEnabled** | When set to True, the owning application of the container type can support archival of containers. Archive helps in saving cost of storage by moving inactively used content to cold tier. |
 
 The [Set-SPOContainerType](/powershell/module/sharepoint-online/Set-SPOContainerType) cmdlet allows admins to update the Application Redirect URL. The [Set-SPOContainerTypeConfiguration](/powershell/module/sharepoint-online/Set-SPOContainerTypeConfiguration) cmdlet allows admins to add host URLs, set [Microsoft 365 content discoverability](../development/content-experiences/user-experiences-overview.md) and [sharing](../development/sharing-and-perm.md) settings on container types. The setting applies to all container instances of the container type.
 
@@ -247,7 +248,7 @@ To create and interact with containers, you must [register](register-api-documen
 
 ## Deleting Container Types
 
-Developer admins can delete both trial and standard container types. To delete a container type, you must first remove all containers of that container type, including those from the deleted container collection. To remove containers, refer to [Consuming Tenant Admin](../administration/consuming-tenant-admin/cta.md).
+Developer admins can delete both trial and standard container types. To delete a container type, you must first remove all containers of that container type, including those from the archived as well as deleted container collection. To remove containers, refer to [Consuming Tenant Admin](../administration/consuming-tenant-admin/cta.md).
 Once all the containers are deleted, Developer admins can delete the container type using `Remove-SPOContainerType`.
 
 ```powershell

docs/embedded/overview.md

@@ -53,7 +53,7 @@ This includes settings from Microsoft Purview compliance, risk, and security set
 
 Microsoft 365 customers have different entitlements related to storage, usage, and features depending on the licenses the customer has purchased.
 
-The partition created in the consumer’s Microsoft 365 tenant by a SharePoint Embedded app doesn’t count towards other Microsoft 365 entitlements including the total amount of Microsoft SharePoint storage that can be used by your organization. Instead, the partition in the consumer’s Microsoft 365 tenant by the SharePoint Embedded app are billed separately through an Azure subscription on a pay-as-you-go metered consumption model that’s based on total storage and the number of API calls.
+The partition created in the consumer’s Microsoft 365 tenant by a SharePoint Embedded app doesn’t count towards other Microsoft 365 entitlements including the total amount of Microsoft SharePoint storage that can be used by your organization. Instead, the partition in the consumer’s Microsoft 365 tenant by the SharePoint Embedded app are billed separately through an Azure subscription on a pay-as-you-go metered consumption model that’s based on total storage in active and archived state and the number of API calls.
 
 > [!NOTE]
 > Learn more about billing for SharePoint Embedded, see [Billing Meters](./administration/billing/meters.md).