You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/embedded/concepts/app-concepts/containertypes.md
+20-16Lines changed: 20 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: SharePoint Embedded Container Types
3
3
description: This article explains how Container Types work.
4
-
ms.date: 07/30/2024
4
+
ms.date: 02/17/2025
5
5
ms.localizationpriority: high
6
6
---
7
7
@@ -31,10 +31,7 @@ A container type can be created for trial/development purposes and isn't linked
31
31
- Use 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.
The following restrictions are applied to container type in the trial status:
@@ -47,24 +44,31 @@ The following restrictions are applied to container type in the trial status:
47
44
48
45
## Standard/Non-trial use
49
46
50
-
Container type can also be created with an Azure billing profile, which includes an Azure Subscription ID and a Region Group. This container typeis in the standard status and is billable. You need the following to create a container type in the standard status:
47
+
A standard container type, by definition, has a billing profile associated with it and can be either regular billed or direct to consumer billed. A standard container type is created using the [New-SPOContainerType](./New-SPOContainerType.md) cmdlet . In case of regular billing, the next step after creation is the addition of a billing profile using the [Add-SPOContainerTypeBilling](./Add-SPOContainerTypeBilling.md) cmdlet. With the use of `-IsPassThroughBilling`, you can create a direct to customer billed container type. There is no need to attach a billing profile in case this case. You need the following to create a container type in the standard status:
51
48
52
-
- An Azure subscription and Resource Group must be present in the Azure portal
49
+
- An Azure subscription and Resource Group must be present in the Azure portal, in case of regular billed.
53
50
- An App registration must be created in Microsoft Entra ID
54
-
- Each developer tenant can create up to five container types in the standard status. To create one, use the following PowerShell cmdlet:
51
+
- Each developer tenant can create up to five container types in the standard status.
52
+
53
+
To create a regular billed, standard container type, use the following cmdlets:
> The user or admin who will set up a billing relationship for SharePoint Embedded will need to have owner or contributor permissions on the Azure subscription.
67
65
66
+
To create a direct to customer billed, standard container type, use the following cmdlet:
Developer Admin can view all the SharePoint Embedded container types created by them on their tenant using this PowerShell cmdlet. This cmdlet retrieves and returns the list of container types created for a SharePoint Embedded Application in the tenant.
81
85
82
86
```powershell
83
-
Get-SPOContainerType
87
+
Get-SPOContainerType [<CommonParameters>]
84
88
```
85
89
86
90
Example output of the `Get-SPOContainerType` cmdlet
@@ -101,7 +105,7 @@ To create and interact with containers, you must [register](../app-concepts/regi
101
105
102
106
## Deleting Container Types
103
107
104
-
Developer Admins can only delete container types in trial status. To delete a container type in trial status, you must remove all containers of the container type first, including from the deleted container collection. To remove containers, refer to [Consuming Tenant Admin](../admin-exp/consuming-tenant-admin/cta.md). Once all the containers are deleted, Developer Admins can delete the container types using the below PowerShell cmdlet.
108
+
Developer admins can delete container types of both trial and standard status. To delete a container type, you must remove all containers of the container type first, including from the deleted container collection. To remove containers, refer to [Consuming Tenant Admin](../admin-exp/consuming-tenant-admin/cta.md). Once all the containers are deleted, Developer admins can delete the container type using the below PowerShell cmdlet.
0 commit comments