Home > Exchange Online Public Folder Migration
Export to PDFThe following tables detail the supported and unsupported elements for Exchange Online Public Folder to Exchange Online Shared Mailbox.
√ – Supported; × –Unsupported.
| Object Type | App Profile Support Status | Service Account Authentication Support Status | Comment |
|---|---|---|---|
| Mail and Post Items | √ | √ | |
| Calendar Items | √ | √ | Refer to Comment 1 below the table. |
| Contact Items | √ | √ | |
| Journal Items | √ | √ | |
| Notes Items | √ | √ | |
| Task Items | √ | √ | |
| Public Folder Permission | × | × | When migrating to shared mailboxes, public folder permissions cannot be migrated. |
Comment 1:
The link of a Skype for Business meeting on the calendar will not be replaced with the destination link after the migration.
If you do not keep the domain of the source environment to the destination, enable the Replace email addresses of senders/recipients based on user mappings setting in the Exchange Online Public Folder migration policy to replace the recipients' email addresses with the corresponding email addresses in the destination. However, in the following cases, source users are not replaced with the destination users after the migration:
When the organizer views the calendar item in the destination, the source organizer/attendees are replaced with the destination users, but when the attendees view the calendar item, the source users are not replaced with the destination users.
Though attendees have accepted a calendar item in the source, after the migration, when the organizer views the migrated item in the destination, there is no user responding to the event, and the organizer is added to the Didn't respond list.
If you enable the Replace meeting links with the destination information setting in the Exchange Online Public Folder migration policy to replace the source meeting link with a destination link, make sure you have configured user mappings for the source meeting organizers. There are some notes that need your attention. Refer to the Notes When Replacing Meeting Links section below for details.
| Object Type | App Profile Support Status | Service Account Authentication Support Status | Comment |
|---|---|---|---|
| √ | √ | ||
| Post | √ | √ | |
| Appointment | √ | √ | Appointment is a calendar item and follows the limitations of calendars. |
| Meeting | √ | √ | Meeting is a calendar item and follows the limitations of calendars. |
| Contact | √ | √ | |
| Task | √ | √ | |
| Note | √ | √ | |
| Journal Entry | √ | √ |
| Object Type | App Profile Support Status | Service Account Authentication Support Status | Comment |
|---|---|---|---|
| Flag | √ | √ | |
| Mark as Read/Unread | × | × | The read/unread information of public folders per-user cannot be migrated to the destination. |
| Follow Up | √ | √ | |
| Category | Partially Supported | Partially Supported | The custom categories can be migrated to the destination, but the color of the custom categories will be displayed in grey in the destination. |
| Sensitivity label of email | Partially Supported | Partially Supported | The emails encrypted by external users cannot be decrypted and cannot be migrated. |
| Attachment | √ | √ | |
| Reply status of meeting participants | × | × | |
| Sharing Permissions | × | × |
| Object Type | App Profile Support Status | Service Account Authentication Support Status | Comment |
|---|---|---|---|
| Folder Delegation | × | × |
If you enable the Replace meeting links with the destination information setting to replace the source meeting link with a destination link, some issues may occur in the following situations:
Due to API limitations, some features may be different from the source after users join the meeting with the new links.
If destination organizers join the meeting via Teams on the web:
Chat, Apps, Record and translation, and Meeting notes actions are not available.
The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info.
The Turn off incoming video action will not be displayed in More > Settings, but will be displayed in View > More options.
Only the current user will be displayed in the meeting.
The meeting duration will not be displayed.
The options in Meeting options displayed in More > Settings will not be displayed.
If destination attendees join the meeting via Teams on the web:
Chat, Apps, Record and translation, and Meeting notes actions are not available.
The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info.
The Turn off incoming video action will not be displayed in More > Settings, but will be displayed in View > More options.
Only the current user will be displayed in the meeting.
The meeting duration will not be displayed.
If destination organizers join the meeting via the Teams app:
Chat, Apps, Record and translation, and Meeting notes actions are not available.
Only the current user will be displayed in the meeting.
The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info.
The meeting duration will not be displayed.
The options in Meeting options displayed in More > Settings will not be displayed.
If destination attendees join the meeting via the Teams app:
Chat, Apps, Record and translation, and Meeting notes actions are not available.
Only the current user will be displayed in the meeting.
The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info.
The meeting duration will not be displayed.
The Meeting options link in the calendar cannot be opened.
The source tenant ID in the meeting link will be replaced with the destination information. If some users in your organization have been migrated to the destination and the meeting participants contain source users and users who have been migrated to the destination, when the source and destination participants click the meeting links in the email, they will enter two different meetings.
The source tenant ID in the meeting link will be replaced with the destination information. If the meeting participants contain external users, the destination meeting organizer needs to update the meeting after the migration to update the meeting link for external users. Otherwise, when external users click the link to attend the meeting, they will be redirected to the source meeting.