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.
New Sample - Migrate Teams Channels #914
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.
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
Uh oh!
There was an error while loading. Please reload this page.
New Sample - Migrate Teams Channels #914
Changes from all commits
a970142fa12db41712572File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Migrate Teams Channel Messages
Summary
This script provides a solution for migrating Teams channel content using the Microsoft Graph API with certificate-based authentication. It creates a new channel in the destination Team and migrates all messages, replies, and files while maintaining the original conversation structure and timestamps. This can also upgrade Standard Channels to Shared or Private Channels.
The script follows these steps:
Features
What Gets Migrated
What Doesn't Get Migrated
Prerequisites
Required Microsoft Graph Application Permissions
Your Azure AD application must have the following Application permissions (not Delegated):
Teamwork.Migrate.All- CRITICAL for message migration with historical timestampsUser.ReadBasic.All- To look up user informationChannelMessage.Read.All- To read messages from source channelChannel.ReadBasic.All- To read channel informationChannel.Create- To create destination channelTeam.ReadBasic.All- To read team informationFiles.ReadWrite.All- To copy channel files from SharePointUsage
Basic Migration (Standard Channel)
Migration with Fallback User
For handling messages from deleted users, bots, and apps:
Migrate to a Private Channel
Microsoft Graph PowerShell
[!INCLUDE More about Microsoft Graph PowerShell SDK]
Contributors
[!INCLUDE DISCLAIMER]