-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New command: spo site unarchive
#6019
Comments
Seems solid 👍
|
I don't mind, however, as far as I know, we don't do this like this at other places.
In that case, I'd opt for a separate command, no? I also don't know if this is something that people want to do because every restored site is billed (unless it's been archived less than 7 days ago). |
also does this need to be an absolute URL? I think we support specifying just the relative path as CLI is aware of the host part of the URL right? |
Correct. Lets leave it as is then 👍
Good point. If anything that also could be a script sample rather than a command👍 |
Technically speaking, yes. But as far as I know, we support this anywhere. That's something we could implement for all commands, like |
Aw yeah, totally forgot spo commands transform all URLs by default 😊 |
Can I work on this? |
Usage
m365 spo site unarchive [options]
Description
Unarchives a site collection
Options
-u, --url <url>
-f, --force
Examples
Unarchive a specific site collection
m365 spo site unarchive --url "https://contoso.sharepoint.com/sites/Marketing"
Unarchive a specific site collection without confirmation prompt
m365 spo site unarchive --url "https://contoso.sharepoint.com/sites/Marketing" --force
Default properties
No response
Additional Info
API request
Since the REST API request is an internal request, we prefer to use the CSOM request.
Remarks
Note
Info admonition: To use this command you must be a Global or SharePoint administrator.
Warning
If a site remains archived for more than seven days, the reactivation fee will be calculated based on the entire storage capacity of the site.
Additional info
The text was updated successfully, but these errors were encountered: