Skip to content

Commit 4c479ee

Browse files
authored
Update containertypes.md
1 parent 53e6d68 commit 4c479ee

File tree

1 file changed

+20
-16
lines changed

1 file changed

+20
-16
lines changed

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

Lines changed: 20 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: SharePoint Embedded Container Types
33
description: This article explains how Container Types work.
4-
ms.date: 07/30/2024
4+
ms.date: 02/17/2025
55
ms.localizationpriority: high
66
---
77

@@ -31,10 +31,7 @@ A container type can be created for trial/development purposes and isn't linked
3131
- 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.
3232

3333
```powershell
34-
New-SPOContainerType
35-
[–TrialContainerType]
36-
[ -ContainerTypeName <ContainerTypeName>]
37-
[ -OwningApplicationId <OwningApplicationId>]
34+
New-SPOContainerType [–TrialContainerType] [-ContainerTypeName] <String> [-OwningApplicationId] <String> [-ApplicationRedirectUrl] <String> [<CommonParameters>]
3835
```
3936

4037
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:
4744

4845
## Standard/Non-trial use
4946

50-
Container type can also be created with an Azure billing profile, which includes an Azure Subscription ID and a Region Group. This container type is 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:
5148

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.
5350
- 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:
54+
55+
```powershell
56+
New-SPOContainerType [-ContainerTypeName] <String> [-OwningApplicationId] <String> [-ApplicationRedirectUrl] <String> [<CommonParameters>]
57+
```
5558

5659
```powershell
57-
New-SPOContainerType
58-
[–ContainerTypeName <ContainerTypeName>]
59-
[-OwningApplicationId <OwningApplicationId>]
60-
[-AzureSubscriptionId <AzureSubscriptionId>]
61-
[-ResourceGroup <ResourceGroup>]
62-
[-Region <Region>]
60+
Add-SPOContainerTypeBilling –ContainerTypeId <ContainerTypeId> -AzureSubscriptionId <AzureSubscriptionId> -ResourceGroup <ResourceGroup> -Region <Region>
6361
```
6462

6563
> [!NOTE]
6664
> 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.
6765
66+
To create a direct to customer billed, standard container type, use the following cmdlet:
67+
68+
```powershell
69+
New-SPOContainerType [-ContainerTypeName] <String> [-OwningApplicationId] <String> [-ApplicationRedirectUrl] <String> [-IsPassThroughBilling] [<CommonParameters>]
70+
```
71+
6872
## Configuring Container Types
6973

7074
Developer Admin can set selected settings on the SharePoint Embedded container types created by using this PowerShell cmdlet.
@@ -80,7 +84,7 @@ Set-SPOContainerTypeConfiguration -ContainerTypeId 4f0af585-8dcc-0000-223d-661eb
8084
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.
8185

8286
```powershell
83-
Get-SPOContainerType
87+
Get-SPOContainerType [<CommonParameters>]
8488
```
8589

8690
Example output of the `Get-SPOContainerType` cmdlet
@@ -101,7 +105,7 @@ To create and interact with containers, you must [register](../app-concepts/regi
101105

102106
## Deleting Container Types
103107

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.
105109

106110
```powershell
107111
Remove-SPOContainerType

0 commit comments

Comments
 (0)