CTMM Update - #2570
Open
guruxp wants to merge 1 commit into
Open
Conversation
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates CrossTenantMailboxMigrationValidation.ps1 to allow -CollectSourceOnly data collection without requiring -CSV, enabling config-only source tenant exports for scenarios where mailbox lists are not available/needed.
Changes:
- Updated comment-based help and examples to document config-only
-CollectSourceOnlybehavior when-CSVis omitted. - Made
-CSVnon-mandatory for theCollectModeparameter set and updated help messages accordingly. - Refactored
-CollectSourceOnlyexecution flow to always collect org-level configuration, and conditionally collect per-mailbox data only when a valid CSV is provided.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue:
There was a specific scenario for data collection where customers could not export tenant config on source tenants only without specifying a list of users.
Reason:
This change addresses the issue by making sure the CSV parameter is not mandatory on the parameter set used for SDP
Fix:
Removed the mandatory for CSV parameter under the parameter set used for CollectSourceOnly and added the logic to detect whether CSV was used or not and if used then pull the info for the users, otherwise just pull config only from source tenant.
Validation:
PS C:\CSS-Exchange\CSS-Exchange\dist> .\CrossTenantMailboxMigrationValidation.ps1 -CollectSourceOnly -PathForCollectedData c:\temp\ -LogPath c:\temp\CTMM2.log
WARNING: This script appears to be an unsigned test build. Skipping version check.
Transcript started, output file is c:\temp\CTMM2.log
Informational: Saving SOURCE tenant id to text file
Informational: Exporting the SOURCE tenant organization relationships
Informational: Checking if there's a published scope defined on the organization relationships to extract the members
Informational: CTMM organization relationship doesn't match for a cross tenant mailbox migration scenario
Informational: O365 to On-premises - af46d263-531d-481f-97af-ef4c9cf7ac13 organization relationship doesn't match for a cross tenant mailbox migration scenario
Informational: No CSV file was specified, only SOURCE tenant/org level configuration will be collected (no mailbox-specific data)
Informational: Source data has been exported. Compressing it into a ZIP file
Informational: ZIP file has been generated with a total of 3 files, and can be found at c:\temp\CTMMCollectedSourceData.zip so it can be sent to the target tenant administrator, however you can still access the raw data at c:\temp\3007261007
Transcript stopped, output file is C:\temp\CTMM2.log