corso/website/docs/support/known-issues.md
ashmrtn a6ec08375f
Fix in-place contacts restore when restore destination is empty (#5053)
Fix bug where we tried to create folders with an empty display name
when the user did a restore with `/` or `""` as the restore destination
for contacts

This PR is safe with the current flow for backing up contact folders
because nested folders aren't backed up at all (at least nesting beyond
the first level). It is unclear, though possible, that this patch will
continue to work if we backup nested contact folders

Also adds basic smoke tests for this issue for all exchange data types

---

#### Does this PR need a docs update or release note?

- [x]  Yes, it's included
- [ ] 🕐 Yes, but in a later PR
- [ ]  No

#### Type of change

- [ ] 🌻 Feature
- [x] 🐛 Bugfix
- [ ] 🗺️ Documentation
- [ ] 🤖 Supportability/Tests
- [ ] 💻 CI/Deployment
- [ ] 🧹 Tech Debt/Cleanup

#### Test Plan

- [x] 💪 Manual
- [x]  Unit test
- [ ] 💚 E2E
2024-01-18 23:50:50 +00:00

2.1 KiB

Known issues

Below is a list of known Corso issues and limitations:

  • Corso supports Exchange (email, calendars, contacts), OneDrive (files) and SharePoint (Document Libraries) M365 data. Additional data types and services will be added in subsequent releases.

  • Backups of Exchange email may not include changes to the read status of an email if no other changes to the email have been made since the previous backup.

  • Restoration of Nested attachments within Exchange Mail or Calendars aren't yet supported.

  • Folders and Calendars containing zero items or subfolders aren't included in the backup.

  • Provides no guarantees the inclusion of data that's moved, added, or deleted from M365 while a backup creation is running. The next backup creation will correct any missing data.

  • Sharing information of items in OneDrive/SharePoint using sharing links aren't backed up and restored.

  • Permissions/Access given to a site group can't be restored.

  • If a link share is created for an item with inheritance disabled (via the Graph API), the link shares restored in that item will not be inheritable by children.

  • Link shares with password protection can't be restored.

  • Teams conversation replies are only backed up if the parent message is available at the time of backup.

  • Groups SharePoint files don't support Export. This limitation will be addressed in a follow-up release

  • Teams messages don't support Restore due to limited Graph API support for message creation.

  • Groups and Teams support is available in an early-access status, and may be subject to breaking changes.

  • Restoring the data into a different Group from the one it was backed up from isn't currently supported.

  • Backing up a group mailbox item may fail if it has a large number of attachments (500+).

  • Exchange in-place restore may restore items in well-known folders to different folders if the user has well-known folder names change based on locale and has updated the locale since the backup was created.

  • In-place Exchange contacts restore will merge items in folders named "Contacts" or "contacts" into the default folder.