Features (Supported & Not Supported)
Feature Point |
Description |
Demo Version License |
Only two users |
Date Filter |
From [on Sent/Received Date] |
Folder Structure |
Maintained as in Origin |
Special Characters / Foreign Language Names For Folders |
Supported |
Folder Name Existing conflicts |
Yes, It Creates with incremental counter. |
Max PST Path Length |
200 |
Max Folder Name Length |
254 |
Max File Name Length |
50 |
Trash |
Not Supported |
Attachments |
Supported [attachment from Onedrive will not be supported] |
Date Time Retention |
Supported |
Maximum PST file Size |
30 GB If PST file cross 30 GB then new PST will get created and data will be stored in new PST. |
PST file Naming Convention |
default file will be created with “user email address.pst” and in case of crossing limit file will be created with incremental counter. |
Default Folder Mapping |
Supported |
Read/Unread |
Supported |
Conversation |
Supported |
Mail Body Format
[ RTF, HTML and Plain Text]
|
Supported |
Priority |
Supported
|
Delta |
Supported
|
User Concurrency |
Supported 4 Users
|
Permissions |
Not Supported
|
On behalf |
Supported |
Shortcomings and Limitations
Limitation |
Reason |
All folders present even if they are outside the date filter’s range |
The application is designed to pre-process the folders first and then the files. |
Forward slash [ / ] in Folder name |
Not Supported [As we are using this as path separator] |
Known Issues
Issue |
Reason |
OutOFMemoryException |
From Microsoft and Aspose API EndPoint |
APIS
- The application is using the microsoft graph Api Version [Need to check]
- Graph API :
Aspose Api 18.6 version
Conclusion
- Large mails fail if not completed within timeout duration of 3 mins. Requests will be retried 5 times.
- In-Place archive is a backup of the entire account taken by the Office 365. We currently haven't studied this case.
- Read/Write can fail is the MIME is invalid
- Shared Calendar/ Permission folders / Calendar Invitation mail can get skipped if they are not accessible to the user.
- No Translation between different language accounts is supported. Hence, source and destination need to be in same language. This will be updated in prerequisite.
Other Pre-Requisites for Backup Contacts
- The source account should be having a valid licens
- Provide the UPN.
- The source domain should be having Contacts.Read(Graph) permissions granted on the Azure project
- Local destination folder must be granted with write permission.
- .Net Framework 4.6.1
Features (Supported & Not Supported)
Feature Point |
Description |
Demo Version License |
Only two users |
Date Filter |
From - To Supported [on Created Date] |
Folder Structure |
Original Structure Maintained |
Special Characters / Foreign Language Names For Folders |
Yes, if in accordance with Outlook rules |
Folder Name Existing conflicts |
Folders remain unaffected (need to check) |
Multiple Email addresses |
Supported |
Phone :Business,home and mob(1) |
Supported |
Chat |
Supported (Mapped to IM address) |
Yomi company ,first name,last name |
Supported
|
Work (Job title,department,company name,manager,assistant name) |
Supported
|
Notes |
Supported
|
Profile Photo |
Supported
|
Personal Info - First Name,Last Name,Suffix,Prefix |
Supported
|
Addresses : Business,Home ,Other |
Supported
|
Other: Nick Name, Birthday |
Supported
|
Significant Other |
Supported (Mapped to Chat) |
Other : Anniversary,Location |
Supported |
Follow up Contacts |
Not Supported |
School |
Supported |
Delta Backup |
Supported |
Fax (Home,Business,Other) |
Not Supported |
Suffix |
Supported |
Personal Web Page |
Not Supported |
Shortcomings and Limitations
Limitation |
Reason |
All folders present even if they are outside the date filter’s range |
The application is designed to preprocess the folders first and then the contacts. |
Known Issues
Issue |
Reason |
Callback,Car_Phone_Number, Fax1, EmailAddress,Pager,ISDN,Radio,Primary, Telex, TTY |
no API endpoint |
List and Groups not supported |
no API endpoint |
Deleted items |
no API endpoint |
Directory |
no API endpoint |
Follow up Contacts |
no API endpoint |
frequently contact list |
no API endpoint |
Favorites |
no API endpoint |
Requests Timed Out in Logs |
Slow Internet connection |
Assistant Phone |
no API endpoint |
Account configured to outlook |
not supported |
Linked Contact |
Will not be display as linked but treat as separate contact |
API
- The application is using the Microsoft Graph API which a REST based API for interacting with Office 365
- Graph API :
- https://docs.microsoft.com/en-us/graph/api/overview?view=graph-rest-1.0
https://docs.microsoft.com/en-us/graph/api/resources/contact?view=graph-rest-1.0
https://docs.microsoft.com/en-us/graph/outlook-get-shared-contacts-folders
- Aspose API (20.3.0):
https://docs.aspose.com/display/emailnet/Working+with+Outlook+Contacts
https://apireference.aspose.com/email/net/aspose.email.personalinfo/contact
API Request Volume Limit : 10000 requests every 10 minutes.
Other Pre-Requisites for Backup Calendars
- The destination account should be having a valid license.
- Provide the UPN.
- The source domain should be having Calendar.Read(Graph). Permissions granted on the Azure project.
- The destination domain should be having Calendars.ReadWrite.All, full_access_as_app(Exchange) Calendars.ReadWrite.All, permissions granted on the Azure project.
- For writing calendar attendees we are using Exchange API.
Features (Supported & Not Supported)
Feature Point |
Description |
Demo Version License |
Max 2 user mailboxes are supported |
Folder Structure |
Flat level Hierarchy Supported |
PST file Naming Convention |
default file will be created with “user email address .pst and
in case of crossing limit file will be created with incremental counter. |
Local Attachment |
Up to 4 MB request supported |
Date Filter |
Supported [on the Start Date] |
Delta Backup |
Supported |
Special Characters / Foreign Language Names |
Supported |
Recurrence |
Supported |
Folder Color |
Not Supported |
Attendees |
Supported |
Resources |
Supported |
Notification |
Supported |
Future Events |
up to +1 year supported |
All Day Event |
Supported |
Reminder |
Supported |
Categories |
Not Supported |
Location |
Supported |
Other Calendars |
Supported (samples not provided) |
Visibility |
Supported |
Time zone mapping |
Supported |
Private and public |
Supported |
Attendees status |
Not Supported |
Read-only calendars |
Not Supported |
Imported / web calendars |
Not Supported |
Charm |
Not Supported |
System calender's |
Supported and mapped to destination system calendar(need to check for non english system folder) |
Subscribed Calendar |
Not Supported |
Shared Calendar / Shared Calendar Folder |
Not Supported |
Group Calendars |
Not Supported |
Birthday Calendars |
Not Supported |
United States Holiday |
Not Supported |
Shortcomings and Limitations
Limitation |
Reason |
All folders present even if they are outside the date filter’s range |
The application is designed to pre-process the folders first and then the files. |
User Categories aren’t automatically migrated. |
The feature is yet to be implemented |
Known Issues
Issue |
Reason |
Requests Timed Out in Logs |
Slow Internet connection |
Organizer |
For this iteration we are maintaining organizer in required list.[in this case organizer will mapped with configured user] |
API Limitation
- The application is using the Microsoft Graph API which a REST based API for interacting with Office 365, also Microsoft Exchange Web Service API is used for Outlook 365 communication
- Graph API : https://docs.microsoft.com/en-us/graph/api/overview?view=graph-rest-1.0
- Aspose.Email 20.3
- API Request Volume Limit : 10000 requests every 10 minutes.
Other Pre-Requisites to Backup Documents
- The source account should be having a valid license.
- The source domain should be having Files.Read.All permissions granted on the Azure project
- Account should be pre-provision.
- Local destination folder must be granted with writing permission.
Features (Supported & Not Supported)
Feature Point |
Description |
Demo Version License |
Only two users |
Date Filter |
From - To supported [Modified Date Time]
|
Folder Structure |
Original Structure Maintained |
Max Path Lenth |
250
|
Max File Name Length |
50 |
Max Folder Name lenth |
50 |
File Versions |
Not Supported |
File Timestamps |
Not Supported |
Trash |
Not Supported |
Shared With Me |
Not Supported |
Recent |
Not Supported |
Special Characters / Foreign Language Names |
Yes, Followed by windows system configuration. [Which are not supported are replaced with '_'] |
File/Folder Name Existing conflicts |
Yes, It Creates with incremental counter. |
Empty Files (0 Size) |
Supported. |
Delta Backup
|
Supported
|
Shared Drives |
Existing files/folders are preserved untouched, new additions in source are migrated.
|
creation / modification date |
Not Supported |
Permissions |
Not Supported |
Limtations
Limitations |
Description |
Version History not migrated |
Additional overheads
|
OneNote |
no API endpoint
|
Shared Libraries |
no API endpoint
|
Discover folders |
no API endpoint
|
SharePoint |
not supported
|
API
The application is using the Microsoft Graph API which a REST based API for interacting with Office 365.
Reference :https://docs.microsoft.com/en-us/graph/api/overview?view=graph-rest-1.0