Skip to content

[AutoPublish] main to live - 08/13 10:30 PDT | 08/13 23:00 IST #13052

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.

Sign up for GitHub

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

Merged
merged 9 commits into from
Aug 13, 2025
Merged

[AutoPublish] main to live - 08/13 10:30 PDT | 08/13 23:00 IST #13052

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
efcfed4
30 days data in AE
mayanksahu11 Aug 13, 2025
40e5f41
Removing EXO references to BadItemLimit and LargeItemLimit
guruxp Aug 13, 2025
36ddaa6
Merge branch 'main' into patch-10
chrisda Aug 13, 2025
0737f26
Merge pull request #13049 from mayanksahu11/patch-10
chrisda Aug 13, 2025
683621c
Update New-MigrationBatch.md
chrisda Aug 13, 2025
46253cc
Update New-MigrationBatch.md
chrisda Aug 13, 2025
fda7780
Update New-MigrationBatch.md
chrisda Aug 13, 2025
1ad3324
Merge branch 'main' into patch-12
chrisda Aug 13, 2025
46f8a96
Merge pull request #13051 from guruxp/patch-12
chrisda Aug 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ title: Export-ActivityExplorerData
## SYNOPSIS
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).

Use the Export-ActivityExplorerData cmdlet to export activities from Data classification \> Activity Explorer in the Microsoft 365 Purview compliance portal.
Use the Export-ActivityExplorerData cmdlet to export activities from Data classification \> Activity Explorer in the Microsoft 365 Purview compliance portal. Activity explorer reports on up to 30 days worth of data.

For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).

Expand Down
40 changes: 19 additions & 21 deletions exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,15 +199,12 @@ New-MigrationBatch -Name <String> -CSVData <Byte[]> [-DisallowExistingUsers]
[-AllowIncrementalSyncs <Boolean>]
[-AllowUnknownColumnsInCsv <Boolean>]
[-ArchiveDomain <String>]
[-ArchiveOnly]
[-AutoComplete]
[-AutoRetryCount <Int32>]
[-AutoStart]
[-BadItemLimit <Unlimited>]
[-CompleteAfter <DateTime>]
[-Confirm]
[-DomainController <Fqdn>]
[-LargeItemLimit <Unlimited>]
[-Locale <CultureInfo>]
[-MoveOptions <MultiValuedProperty>]
[-NotificationEmails <MultiValuedProperty>]
Expand Down Expand Up @@ -236,13 +233,11 @@ New-MigrationBatch -Name <String> [-CSVData <Byte[]>] [-DisallowExistingUsers] [
[-AllowIncrementalSyncs <Boolean>]
[-AllowUnknownColumnsInCsv <Boolean>]
[-ArchiveDomain <String>]
[-ArchiveOnly]
[-AutoComplete]
[-AutoProvisioning]
[-AutoRetryCount <Int32>]
[-AutoStart]
[-AvoidMergeOverlap]
[-BadItemLimit <Unlimited>]
[-CompleteAfter <DateTime>]
[-Confirm]
[-ContentFilter <String>]
Expand All @@ -254,7 +249,6 @@ New-MigrationBatch -Name <String> [-CSVData <Byte[]>] [-DisallowExistingUsers] [
[-ForwardingDisposition <GmailForwardingDisposition>]
[-IncludeFolders <MultiValuedProperty>]
[-IncludeOtherContacts]
[-LargeItemLimit <Unlimited>]
[-Locale <CultureInfo>]
[-MigrateTasks]
[-MoveOptions <MultiValuedProperty>]
Expand Down Expand Up @@ -637,7 +631,7 @@ Accept wildcard characters: False

> Applicable: Exchange Online

This parameter is available only in the cloud-based service.
able only in the cloud-based service.

{{ Fill Analyze Description }}

Expand All @@ -657,7 +651,7 @@ Accept wildcard characters: False

> Applicable: Exchange Online

This parameter is available only in the cloud-based service.
able only in the cloud-based service.

{{ Fill ManagedGmailTeams Description }}

Expand Down Expand Up @@ -717,7 +711,7 @@ Accept wildcard characters: False

> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE

This parameter is available only in on-premises Exchange.
able only in on-premises Exchange.

The Local switch specifies a local move (mailboxes are moved to a different mailbox database in the same Active Directory forest). You don't need to specify a value with this switch.

Expand All @@ -737,7 +731,7 @@ Accept wildcard characters: False

> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE

This parameter is available only in on-premises Exchange.
able only in on-premises Exchange.

The SourcePublicFolderDatabase parameter specifies the source public folder database that's used in a public folder migration. You can use any value that uniquely identifies the database. For example:

Expand All @@ -761,7 +755,7 @@ Accept wildcard characters: False

> Applicable: Exchange Online

This parameter is available only in the cloud-based service.
able only in the cloud-based service.

{{ Fill AdoptPreexisting Description }}

Expand All @@ -781,7 +775,7 @@ Accept wildcard characters: False

> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE

This parameter is available only in on-premises Exchange.
able only in on-premises Exchange.

The AllowIncrementalSyncs parameter specifies whether to enable or disable incremental synchronization. Valid values are:

Expand Down Expand Up @@ -825,7 +819,7 @@ Accept wildcard characters: False

> Applicable: Exchange Online

This parameter is available only in the cloud-based service.
able only in the cloud-based service.

{{ Fill ArchiveDomain Description }}

Expand Down Expand Up @@ -853,7 +847,7 @@ You can use the TargetArchiveDatabases parameter to specify the database to migr

```yaml
Type: SwitchParameter
Parameter Sets: Local, Onboarding, Offboarding
Parameter Sets: Local
Aliases:

Required: False
Expand Down Expand Up @@ -889,7 +883,7 @@ Accept wildcard characters: False

> Applicable: Exchange Online

This parameter is available only in the cloud-based service.
able only in the cloud-based service.

{{ Fill AutoProvisioning Description }}

Expand All @@ -909,7 +903,7 @@ Accept wildcard characters: False

> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE

This parameter is available only in on-premises Exchange.
able only in on-premises Exchange.

The AutoRetryCount parameter specifies the number of attempts to restart the migration batch to migrate mailboxes that encountered errors.

Expand Down Expand Up @@ -949,7 +943,7 @@ Accept wildcard characters: False

> Applicable: Exchange Online

This parameter is available only in the cloud-based service.
able only in the cloud-based service.

{{ Fill AvoidMergeOverlap Description }}

Expand All @@ -967,13 +961,15 @@ Accept wildcard characters: False

### -BadItemLimit

> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE

This parameter is available only in on-premises Exchange.

The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the migration request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the migration request is ready to complete.

Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again.

**Note**: This parameter is being deprecated in the cloud-based service. In the future, if neither the BadItemLimit or LargeItemLimit parameters are specified, the migration uses Skipped Item approval semantics instead of BadItemLimit semantics.
**Note**: This parameter is deprecated in the cloud-based service.

```yaml
Type: Unlimited
Expand Down Expand Up @@ -1339,7 +1335,9 @@ Accept wildcard characters: False

### -LargeItemLimit

> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE

This parameter is available only in on-premises Exchange.

The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the migration request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.

Expand All @@ -1350,7 +1348,7 @@ For more information about maximum message size values, see the following topics

Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed.

**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
**Note**: This parameter is deprecated in the cloud-based service.

```yaml
Type: Unlimited
Expand Down
Loading