Teams Private Chat Projects
We are excited to announce significant improvements that increase stability and simplify the workflow for Teams Private Chat projects.
- Teams Private Chat is still in preview status at this time.
- Post our PKCE Release on January 19, 2026, GCC High (SharePoint, Teams, Teams Private Chat (PCH), and OneDrive) as source or destination are currently unsupported using MigrationWiz due to Microsoft Enforcement of MFA, we are working on extending PKCE to GCC High endpoints at this time. Although you will see GCC High as an option for endpoint selection, this option is currently not supported.
Teams Private Chat Infrastructure
New infrastructure has been implemented to improve scalability and performance, resulting in planned migrations being completed more quickly.
Teams Private Chat Rehydration
The last 30 days of messages will be rehydrated in the destination Teams app, starting with the most recent posted message in the source conversation.
Chat History for Teams Private Chat
- Users with no history restrictions will receive a link to the full chat history in the conversations they are members of.
- Users with a chat history restriction applied will receive a separate link that reflects the messages they are allowed to view based on their history restrictions settings in the conversations they are members of.
- The chat history HTML files that are shared can be found in the destination service account’s OneDrive at the following folder path:
My files > Microsoft Teams Chat Files > BitTitan MigrationWiz - The chat history HTML files use the following naming conventions
- For files shared with members that have full history visibility:
History_{ChatType}_{SourceOwnerEmail}_{SourceCreatedDateTime}_{TopicSlug}_{AttachmentHash}.html - For files shared with members that have restricted chat history visibility:
History_{ChatType}_{SourceOwnerEmail}_{SourceCreatedDateTime}_{TopicSlug}_{SourceVisibleHistoryStartDateTime}_{AttachmentHash}.html
- For files shared with members that have full history visibility:
New Authentication Requirements for Teams Private Chat
We have added Teams Private Chat to the list of project types that use Microsoft’s more modern identity platform (v2).
What the New Authentication Requirements for Teams Private Chat Provide
- A modern PKCE-based authentication flow
- Enhanced security with Azure Key Vault
- Support for Microsoft’s latest identity platform (OAuth2)
- Simple, UI-based permission selection
- A guided in-UI consent experience for faster setup
- Better compatibility with MFA-enabled tenants
What This Means for You
- A simpler and more intuitive setup through guided, in-UI authentication and consent
- Stronger security controls aligned with Microsoft’s recommended best practices
- Improved reliability across supported Microsoft 365 workloads
- A platform foundation that supports future enhancements and expanded Graph API capabilities
Addition of a Stop Button
A stop button has been added to allow for manual stopping of users in a Teams Private Chat project as needed.