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
@@ -258,7 +261,7 @@ Onboarding and offboarding in Exchange Online
258
261
259
262
- IMAP migration: This onboarding migration type migrates mailbox data from an IMAP server (including Exchange) to Exchange Online. For an IMAP migration, you must first provision mailboxes in Exchange Online before you can migrate mailbox data. For more information, see Example 7.
260
263
261
-
- G Suite migration: This onboarding migration type migrates mailbox data from a G Suite organization to Exchange Online. For a G Suite migration, you must first provision mail users (or mailboxes) in Exchange Online before you can migrate mailbox data.
264
+
- G Suite migration: This onboarding migration type migrates mailbox data from a G Suite organization to Exchange Online. For a G Suite migration, you must first provision mail users (or mailboxes) in Exchange Online before you can migrate mailbox data. For more information, see Example 10.
262
265
263
266
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
This example is the same as Example 8, but the TimeZone parameter is also used. Data migration for the batch will start, but won't complete until 09/01/2018 7:00 PM (PST). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Pacific Standard Time.
A G Suite migration batch is created that uses the CSV migration file gmail.csv and includes the contents of the Paymeng label and only migrate the mails which were received after the time '2019/4/30 00:00' (local system time). This migration batch is pending until it's started with the Start-MigrationBatch cmdlet.
364
+
365
+
351
366
## PARAMETERS
352
367
353
368
### -Name
@@ -669,6 +684,50 @@ Accept pipeline input: False
669
684
Accept wildcard characters: False
670
685
```
671
686
687
+
### -ContentFilter
688
+
This parameter is available only in the cloud-based service.
689
+
690
+
The ContentFilter parameter uses OPath filter syntax to filter the messages by Received date. Only content that match the ContentFilter parameter will be moved to Exchange online. For example:
691
+
692
+
- `"Received -gt '8/23/2020'"`
693
+
- `"Received -le '2019/01/01'"`
694
+
- `"Received -gt '8/23/2015' -and Received -lt '8/23/2020'"`
695
+
696
+
You can specify the language by using the ContentFilterLanguage parameter.
697
+
698
+
```yaml
699
+
Type: String
700
+
Parameter Sets: Onboarding
701
+
Aliases:
702
+
Applicable: Exchange Online
703
+
704
+
Required: False
705
+
Position: Named
706
+
Default value: None
707
+
Accept pipeline input: False
708
+
Accept wildcard characters: False
709
+
```
710
+
711
+
### -ContentFilterLanguage
712
+
This parameter is available only in the cloud-based service.
713
+
714
+
The ContentFilterLanguage parameter specifies the language being used in the ContentFilter parameter for string searches.
715
+
716
+
Valid input for this parameter is a supported culture code value from the Microsoft .NET Framework CultureInfo class. For example, da-DK for Danish or ja-JP for Japanese. For more information, see [CultureInfo Class](https://docs.microsoft.com/dotnet/api/system.globalization.cultureinfo).
717
+
718
+
```yaml
719
+
Type: CultureInfo
720
+
Parameter Sets: Onboarding
721
+
Aliases:
722
+
Applicable: Exchange Online
723
+
724
+
Required: False
725
+
Position: Named
726
+
Default value: None
727
+
Accept pipeline input: False
728
+
Accept wildcard characters: False
729
+
```
730
+
672
731
### -DisableOnCopy
673
732
The DisableOnCopy switch disables the original migration job item for a user if you're copying users from an existing batch to a new batch by using the UserIds or Users parameters.. You don't need to specify a value with this switch.
This parameter is available only in the cloud-based service.
748
807
749
-
For an IMAP migration, the ExcludeFolders parameter specifies mailbox folders that you don't want to migrate from the on-premises messaging system to the cloud-based mailboxes. Use folder names relative to the IMAP root on the on-premises mail server. Specify the value as a string array and separate multiple folder names with commas.
808
+
For an IMAP migration or G Suite migration, the ExcludeFolders parameter specifies mailbox folders that you don't want to migrate from the source email system to the cloud-based mailboxes. Specify the value as a string array and separate multiple folder names with commas.
809
+
810
+
For IMAP migration, use folder names relative to the IMAP root on the source mail server. For G Suite migration, use label names on the source mail server.
811
+
812
+
Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax:
813
+
814
+
`<FolderName>/*`: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, `MyProjects` or `MyProjects/FY2010`.
815
+
816
+
`#<FolderName>#/*`: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, `#Inbox#` denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types:
817
+
818
+
- Inbox
819
+
- SentItems
820
+
- DeletedItems
821
+
- Calendar
822
+
- Contacts
823
+
- Drafts
824
+
- Journal
825
+
- Tasks
826
+
- Notes
827
+
- JunkEmail
828
+
- CommunicatorHistory
829
+
- Voicemail
830
+
- Fax
831
+
- Conflicts
832
+
- SyncIssues
833
+
- LocalFailures
834
+
- ServerFailures
835
+
836
+
If the user creates a personal folder with the same name as a well-known folder and the `#` symbol surrounding it, you can use a back slash (`\`) as an escape character to specify that folder. For example, if a user creates a folder named `#Notes#` and you want to specify that folder, but not the well-known Notes folder, use the following syntax: `\#Notes\#`.
837
+
838
+
Wildcard characters can't be used in folder names.
839
+
840
+
```yaml
841
+
Type: MultiValuedProperty
842
+
Parameter Sets: Onboarding
843
+
Aliases:
844
+
Applicable: Exchange Online
845
+
846
+
Required: False
847
+
Position: Named
848
+
Default value: None
849
+
Accept pipeline input: False
850
+
Accept wildcard characters: False
851
+
```
852
+
853
+
### -IncludeFolders
854
+
This parameter is available only in the cloud-based service.
855
+
856
+
For an IMAP migration or G Suite migration, the IncludeFolders parameter specifies mailbox folders that you want to migrate from the on-premises email system to the cloud-based mailboxes. Use folder names relative to the IMAP root on the source mail server or use label names for G Suite migration. Specify the value as a string array and separate multiple folder names with commas.
857
+
858
+
For IMAP migration, use folder names relative to the IMAP root on the source mail server. For G Suite migration, use label names on the source mail server.
859
+
860
+
Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax:
861
+
862
+
`<FolderName>/*`: Use this syntax to denote a personal folder under the folder specified in the SourceRootFolder parameter, for example, `MyProjects` or `MyProjects/FY2010`.
863
+
864
+
`#<FolderName>#/*`: Use this syntax to denote a well-known folder regardless of the folder's name in another language. For example, `#Inbox#` denotes the Inbox folder even if the Inbox is localized in Turkish, which is Gelen Kutusu. Well-known folders include the following types:
865
+
866
+
- Inbox
867
+
- SentItems
868
+
- DeletedItems
869
+
- Calendar
870
+
- Contacts
871
+
- Drafts
872
+
- Journal
873
+
- Tasks
874
+
- Notes
875
+
- JunkEmail
876
+
- CommunicatorHistory
877
+
- Voicemail
878
+
- Fax
879
+
- Conflicts
880
+
- SyncIssues
881
+
- LocalFailures
882
+
- ServerFailures
883
+
884
+
If the user creates a personal folder with the same name as a well-known folder and the `#` symbol surrounding it, you can use a back slash (`\`) as an escape character to specify that folder. For example, if a user creates a folder named `#Notes#` and you want to specify that folder, but not the well-known Notes folder, use the following syntax: `\#Notes\#`.
750
885
886
+
Wildcard characters can't be used in folder names.
0 commit comments