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
Container is created in an inactive state, as indicated by the status property. A container must be activated within 24 hours after creation, or it will be automatically deleted. Upon activation, the value of the status property changes from inactive to active.
A Container can be activated by calling the activate API, or any other API that updates or modifies the Container or its content. For example, uploading a file to a Container, adding permission to a Container, creating a custom property on a Container, or updating the properties of a Container can activate it.
Nice one! Here I would also clarify the description a bit more. Good catch with the additional information. We should really make sure that this is added as a remark.
Usage
m365 spe container activate [options]
Description
Activates a container
Options
-i, --id <id>
Examples
Activates a container
m365 spe container activate --id "b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z"
Default properties
No response
Additional Info
We should point out in the docs the following:
Container is created in an inactive state, as indicated by the status property. A container must be activated within 24 hours after creation, or it will be automatically deleted. Upon activation, the value of the status property changes from inactive to active.
A Container can be activated by calling the activate API, or any other API that updates or modifies the Container or its content. For example, uploading a file to a Container, adding permission to a Container, creating a custom property on a Container, or updating the properties of a Container can activate it.
we may use the following
POST
request:https://learn.microsoft.com/en-us/graph/api/filestoragecontainer-activate?view=graph-rest-1.0&tabs=http
The text was updated successfully, but these errors were encountered: