Merge pull request MicrosoftDocs#1063 from wrall/master

Update documentation for Exchange Migration cmdlets

Author: chrisda

exchange/exchange-ps/exchange/move-and-migration/Complete-MigrationBatch.md

@@ -34,7 +34,7 @@ After a migration batch for a local or cross-forest move has successfully run an
 
 When the finalization process is complete, you can remove the batch by using the Remove-MigrationBatch cmdlet.
 
-If a migration batch has a status of Completed with Errors, you can rerun the Complete-MigrationBatch cmdlet. The cmdlet will attempt to finalize the failed users.
+If a migration batch has a status of Completed with Errors, you can re-attempt to finalize the failed users. In Exchange Online, use the Start-MigrationBatch cmdlet to retry migration for failed users. In Exchange 2013 or Exchange 2016, use the Complete-MigrationBatch to retry these failed users.
 
 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://technet.microsoft.com/library/mt432940.aspx).
 
@@ -101,6 +101,8 @@ Accept wildcard characters: False
 ```
 
 ### -NotificationEmails
+This parameter is applicable only to on-premises Exchange.
+
 The NotificationEmails parameter specifies one or more email addresses that status reports are sent to after the migration batch is completed. You can specify multiple email addresses separated by commas.
 
 If you don't use this parameter, the final status report is sent to the administrator who runs the Complete-MigrationBatch cmdlet.

exchange/exchange-ps/exchange/move-and-migration/New-MigrationBatch.md

@@ -433,7 +433,19 @@ Accept wildcard characters: False
 ```
 
 ### -CompleteAfter
-This parameter is reserved for internal Microsoft use.
+The CompleteAfter parameter specifies a delay before the batch is completed. The batch is started, but not completed until the date/time you specify with this parameter.
+
+Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format mm/dd/yyyy, enter 09/01/2015 to specify September 1, 2015. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2015 5:00 PM".
+
+In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC).
+
+To specify a date/time value for this parameter, use either of the following options:
+
+- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z".
+
+- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see Get-Date (https://go.microsoft.com/fwlink/p/?LinkID=113313).
+
+This parameter should only be used in the cloud-based service.
 
 ```yaml
 Type: DateTime
@@ -640,7 +652,11 @@ Accept wildcard characters: False
 ```
 
 ### -ReportInterval
-This parameter is reserved for internal Microsoft use.
+The ReportInterval parameter specifies how frequently emailed reports should be sent to the email addresses listed within NotificationEmails.
+
+By default, emailed reports are sent every 24 hours for a batch. Setting this value to 0 indicates that reports should never be sent for this batch.
+
+This parameter should only be used in the cloud-based service.
 
 ```yaml
 Type: TimeSpan
@@ -697,7 +713,19 @@ Accept wildcard characters: False
 ```
 
 ### -StartAfter
-This parameter is reserved for internal Microsoft use.
+The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The batch is started, but the data migration for users within the batch isn't started until the date/time you specify with this parameter.
+
+Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format mm/dd/yyyy, enter 09/01/2015 to specify September 1, 2015. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2015 5:00 PM".
+
+In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC).
+
+To specify a date/time value for this parameter, use either of the following options:
+
+- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z".
+
+- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see Get-Date (https://go.microsoft.com/fwlink/p/?LinkID=113313).
+
+This parameter should only be used in the cloud-based service.
 
 ```yaml
 Type: DateTime

exchange/exchange-ps/exchange/move-and-migration/New-MigrationEndpoint.md

@@ -579,7 +579,7 @@ Accept wildcard characters: False
 ### -Security
 This parameter is available only in the cloud-based service.
 
-The Security parameter specifies the encryption method used by the IMAP server for an IMAP migration. Options are None, SSL (the default), or TLS. This parameter is required when you want to migrate data from an on-premises IMAP server to cloud-based mailboxes.
+For an IMAP migration, the Security parameter specifies the encryption method used by the remote mail server. The options are None, Tls, or Ssl.
 
 ```yaml
 Type: None | Ssl | Tls

exchange/exchange-ps/exchange/move-and-migration/Set-MigrationBatch.md

@@ -145,7 +145,19 @@ Accept wildcard characters: False
 ```
 
 ### -CompleteAfter
-This parameter is reserved for internal Microsoft use.
+The CompleteAfter parameter specifies a delay before the batch is completed. The batch is started, but not completed until the date/time you specify with this parameter.
+
+Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format mm/dd/yyyy, enter 09/01/2015 to specify September 1, 2015. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2015 5:00 PM".
+
+In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC).
+
+To specify a date/time value for this parameter, use either of the following options:
+
+- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z".
+
+- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see Get-Date (https://go.microsoft.com/fwlink/p/?LinkID=113313).
+
+This parameter should only be used in the cloud-based service.
 
 ```yaml
 Type: DateTime
@@ -255,7 +267,11 @@ Accept wildcard characters: False
 ```
 
 ### -ReportInterval
-This parameter is reserved for internal Microsoft use.
+The ReportInterval parameter specifies how frequently emailed reports should be sent to the email addresses listed within NotificationEmails.
+
+By default, emailed reports are sent every 24 hours for a batch. Setting this value to 0 indicates that reports should never be sent for this batch.
+
+This parameter should only be used in the cloud-based service.
 
 ```yaml
 Type: TimeSpan
@@ -287,7 +303,19 @@ Accept wildcard characters: False
 ```
 
 ### -StartAfter
-This parameter is reserved for internal Microsoft use.
+The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The batch is started, but the data migration for users within the batch isn't started until the date/time you specify with this parameter.
+
+Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format mm/dd/yyyy, enter 09/01/2015 to specify September 1, 2015. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2015 5:00 PM".
+
+In Exchange Online, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC).
+
+To specify a date/time value for this parameter, use either of the following options:
+
+- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z".
+
+- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, (Get-Date "5/6/2016 9:30 AM").ToUniversalTime(). For more information, see Get-Date (https://go.microsoft.com/fwlink/p/?LinkID=113313).
+
+This parameter should only be used in the cloud-based service.
 
 ```yaml
 Type: DateTime

exchange/exchange-ps/exchange/move-and-migration/Set-MigrationEndpoint.md

@@ -87,7 +87,7 @@ Accept wildcard characters: False
 ### -Authentication
 This parameter is available only in the cloud-based service.
 
-The Authentication parameter specifies the authentication method used by the on-premises mail server.
+The Authentication parameter specifies the authentication method used by the remote mail server.
 
 ```yaml
 Type: Basic | Digest | Ntlm | Fba | WindowsIntegrated | LiveIdFba | LiveIdBasic | WSSecurity | Certificate | NegoEx | OAuth | Adfs | Kerberos | Negotiate | LiveIdNegotiate | Misconfigured
@@ -295,7 +295,9 @@ Accept wildcard characters: False
 ```
 
 ### -Security
-This parameter is reserved for internal Microsoft use.
+This parameter is available only in the cloud-based service.
+
+For an IMAP migration, the Security parameter specifies the encryption method used by the remote mail server. The options are None, Tls, or Ssl.
 
 ```yaml
 Type: None | Ssl | Tls

exchange/exchange-ps/exchange/move-and-migration/Start-MigrationBatch.md

@@ -25,6 +25,10 @@ Start-MigrationBatch [[-Identity] <MigrationBatchIdParameter>] [-Confirm] [-Doma
 ## DESCRIPTION
 The Start-MigrationBatch cmdlet starts a pending migration batch that was created, but not started, with the New-MigrationBatch cmdlet.
 
+The Start-MigrationBatch cmdlet also will resume a Stopped migration batch or retry failures within a Failed or Synced with Errors migration batch. In the cloud-based service, the Start-MigrationBatch cmdlet can also retry failures within a Completed with Errors migration batch.
+
+In the cloud-based service, the Start-MigrationBatch cmdlet can be run at any time to retry failed users within the batch.
+
 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://technet.microsoft.com/library/mt432940.aspx).
 
 ## EXAMPLES

exchange/exchange-ps/exchange/move-and-migration/Test-MigrationServerAvailability.md

@@ -513,7 +513,7 @@ Accept wildcard characters: False
 ### -Security
 This parameter is available only in the cloud-based service.
 
-The Security parameter specifies the encryption method used by the remote mail server. The options are None, Tls, or Ssl. Use this parameter only when testing the connection to an IMAP server or in preparation for creating a migration endpoint for an IMAP migration.
+For an IMAP migration, the Security parameter specifies the encryption method used by the remote mail server. The options are None, Tls, or Ssl.
 
 ```yaml
 Type: None | Ssl | Tls