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
Copy file name to clipboardExpand all lines: exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ title: Get-MigrationConfig
13
13
## SYNOPSIS
14
14
This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
15
15
16
-
Use the Get-MigrationConfig cmdlet to retrieve migration configuration settings on Exchange servers.
16
+
Use the Get-MigrationConfig cmdlet to retrieve migration configuration settings for your organization.
17
17
18
18
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
19
19
@@ -59,7 +59,7 @@ This example retrieves the settings for the migration configuration.
59
59
60
60
This parameter is available only in the cloud-based service.
61
61
62
-
{{ Fill AllPartitions Description }}
62
+
The AllPartitions switch specifies whether to retrieve the migration configuration from all migration mailbox partitions. You don't need to specify a value with this switch.
This parameter is available only in the cloud-based service.
101
101
102
-
{{ Fill IncludeSimplifiedGmailMigrationData Description }}
102
+
The IncludeSimplifiedGmailMigrationData switch specifies whether to include Gmail-related simplified migration data in the results. You don't need to specify a value with this switch.
Copy file name to clipboardExpand all lines: exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ Use the Set-MigrationEndpoint cmdlet to configure settings for different types o
55
55
- Cutover Exchange migration: Migrate all mailboxes in an on-premises Exchange organization to Exchange Online. Cutover Exchange migration requires the use of an Exchange endpoint.
56
56
- Staged Exchange migration: Migrate a subset of mailboxes from an on-premises Exchange organization to Exchange Online. Staged Exchange migration requires the use of an Exchange endpoint.
57
57
- IMAP migration: Migrate mailbox data from an on-premises Exchange organization or other email system to Exchange Online. For an IMAP migration, you must first create the cloud-based mailboxes before you migrate mailbox data. IMAP migrations require the use of an IMAP endpoint.
58
-
- Gmail migration: Migration mailbox data from a Google Workspace tenant to Exchange Online. For a Google Workspace migration, you must first create the cloud-based mail users or mailboxes before you migrate mailbox data. Google Workspace migrations require the use of a Gmail endpoint.
58
+
- Gmail migration: Migrate mailbox data from a Google Workspace tenant to Exchange Online. For a Google Workspace migration, you must first create the cloud-based mail users or mailboxes before you migrate mailbox data. Google Workspace migrations require the use of a Gmail endpoint.
59
59
- Local: Move mailboxes between different servers or databases within a single on-premises Exchange forest. Local moves don't require the use of an endpoint.
60
60
61
61
For more information about the different move and migration scenarios, see:
This parameter is available only in the cloud-based service.
111
111
112
-
{{ Fill AcceptUntrustedCertificates Description }}
112
+
The AcceptUntrustedCertificates parameter specifies whether to accept untrusted certificates from the remote server. Valid values are $true or $false. This parameter is applicable to ExchangeOutlookAnywhere and IMAP migration endpoints.
This parameter is available only in the cloud-based service.
131
131
132
-
{{ Fill ApplicationId Description }}
132
+
The ApplicationId parameter specifies the application ID of the app registered in Microsoft Entra ID that's used for cross-tenant authentication in ExchangeRemoteMove migration endpoints. Use this parameter together with AppSecretKeyVaultUrl.
This parameter is available only in the cloud-based service.
151
151
152
-
{{ Fill AppSecretKeyVaultUrl Description }}
152
+
The AppSecretKeyVaultUrl parameter specifies the Azure Key Vault URL that contains the application secret used for cross-tenant authentication in ExchangeRemoteMove migration endpoints. Use this parameter together with ApplicationId.
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
191
191
192
192
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
193
-
- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
193
+
- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding.
> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
210
210
211
-
The Credentials parameter specifies the username and password for connecting to the remote endpoint. Credentials should be used when creating either a staged or cutover Exchange endpoint or a RemoteMove endpoint.
211
+
The Credentials parameter specifies the username and password for connecting to the remote endpoint. Credentials should be used when modifying either a staged or cutover Exchange endpoint or a RemoteMove endpoint.
212
212
213
213
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
This parameter is available only in the cloud-based service.
434
434
435
-
For a staged Exchange migration, the RpcProxyServer parameter specifies the FQDN of the RPC proxy server for the on-premises Exchange server. This parameter is only applicable to staged and cutover Exchange endpoints that don't use Autodiscovery
435
+
For staged and cutover Exchange migrations, the RpcProxyServer parameter specifies the FQDN of the RPC proxy server for the on-premises Exchange server. This parameter is only applicable to staged and cutover Exchange endpoints that don't use Autodiscovery
> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
494
494
495
-
The SkipVerification switch skips verifying that the remote server is reachable when creating a migration endpoint. You don't need to specify a value with this switch.
495
+
The SkipVerification switch skips verifying that the remote server is reachable when modifying a migration endpoint. You don't need to specify a value with this switch.
This parameter is available only in the cloud-based service.
617
617
618
-
{{ Fill AcceptUntrustedCertificates Description }}
618
+
The AcceptUntrustedCertificates switch specifies whether to accept untrusted certificates from the remote server. You don't need to specify a value with this switch. This switch is applicable to ExchangeOutlookAnywhere and IMAP endpoint types.
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
659
659
660
660
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
661
-
- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
661
+
- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding.
0 commit comments