Skip to content

Commit 7a145b2

Browse files
committed
Learn Editor: Update Set-SPOContainerTypeConfiguration.md
1 parent 8d7f70c commit 7a145b2

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

sharepoint/sharepoint-ps/Microsoft.Online.SharePoint.PowerShell/Set-SPOContainerTypeConfiguration.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,6 @@ This example sets the host URLs for the container type with Id 4f0af585-8dcc-000
8484

8585
### Example 7
8686

87-
8887
```powershell
8988
Set-SPOContainerTypeConfiguration -ContainerTypeId 4f0af585-8dcc-0000-223d-661eb2c604e4 -IsArchiveEnabled $true
9089
```
@@ -178,14 +177,11 @@ Position: Named
178177
Default value: None
179178
Accept pipeline input: False
180179
Accept wildcard characters: False
181-
182180
```
183181
184-
185182
### -IsArchiveEnabled
186183
187-
Using -IsArchiveEnabled flag, you can start supporting archival and reactivation actions on containers. Archival moves the data in cold tier and offers cost saving benefit. While archived, the content becomes inaccessible and needs to be reactivated first. Reactivation is instantaneous within first 7 days of archival and may take up to 24 hours after that. When not passed, the value of this parameter is set to False and all the calls to archive and unarchive API will fail.
188-
184+
Use the `-IsArchiveEnabled` flag to enable archival and reactivation for containers. Archival moves data to the cold tier, reducing storage costs. While archived, content is inaccessible until reactivated. Reactivation is immediate within the first seven days and can take up to 24 hours afterward. If you don’t include this flag, the value defaults to `False`, and all archive and unarchive API calls fail. After you update the flag, allow up to 24 hours for the change to take effect in the consuming tenant.
189185

190186
```yaml
191187
Type: System.Boolean

0 commit comments

Comments
 (0)