Skip to content

Commit

Permalink
Merge branch 'main' into bhagatshweta-copilotinsights
Browse files Browse the repository at this point in the history
  • Loading branch information
Ruchika-mittal01 authored Dec 12, 2024
2 parents c2ae728 + 2bdf707 commit cc68a3c
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 4 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -103,11 +103,13 @@ The move status for the Office 365 Group. Possible values are:
* InProgress (n/4): The move is in progress in one of the following states: Validation (1/4), Backup (2/4), Restore (3/4), Cleanup (4/4).
* Success: The move has completed successfully.
* Failed: The move failed.
* Stopped: The move was canceled by an administrator while it was still queued.
* NotSupported: The move could not be processed because the Preferred Data Location was invalid.
* Rescheduled: The move did not succeed and is being scheduled again for another attempt.

## NOTES

You can also apply the `-Verbose` option to see additional information about the move.
> [!NOTE]
> You can also apply the `-Verbose` option to see additional information about the move.

## RELATED LINKS

[Move a SharePoint site to a different geo location](https://learn.microsoft.com/office365/enterprise/move-sharepoint-between-geo-locations)
[Move a SharePoint site to a different geo location](/microsoft-365/enterprise/m365-dr-workload-spo)
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,9 @@ The following are the available move states:
|InProgress| The move is in progress in one of the following states: Validation, Backup, Restore, Cleanup.|
|Success| The move has completed successfully.|
|Failed|The move failed.|
|Stopped|The move was canceled by an administrator while it was still queued.|
|NotSupported|The move could not be processed because the Preferred Data Location was invalid.|
|Rescheduled|The move did not succeed and is being scheduled again for another attempt.|

## EXAMPLES

Expand Down

0 comments on commit cc68a3c

Please sign in to comment.