SysTools Outlook.com Backup – Technical Datasheet

Objectives for Outlook.com Email Migration

As a User, I should be able to take back up of Outlook.com account Emails into a PST file so that I can securely store my emails locally and manage them effectively, including optionally deleting the source emails after backup.



Pre-Requisites for Migrating Outlook.com Emails

  • Public project should be created on Azure portal (Applicable for SysTools Domain).
  • Required Free Space on End-User Server for Optimal Backup Performance.
  • Delegate Scopes should be added in azure project
  • User Email Id is required for authentication.
  • Scopes (Delegated)
    • Email - https://graph.microsoft.com/Mail.Read
    • Email Deletion - https://graph.microsoft.com/Mail.ReadWrite
  • offline_access - To get the refresh token that can be used to get new access tokens in the future.
  • openid - The openid scope is the core scope used in OpenID Connect (OIDC), a protocol that builds on OAuth 2.0 for authentication. Application needs to authenticate a user and retrieve user identity information (e.g., their username, email, etc.), the openid scope is necessary.
  • profile - The profile scope requests permission to access the basic profile information(name, given_name, family_name,picture,locale) of the user from the identity provider (such as Google or Microsoft). This typically includes attributes like the user's name, profile picture, and locale.
  • email - The email scope allows the client application to request access to the email address of the authenticated user.


Implementation

  • Public domain account should be Supported.
  • OAuth authentication for office 365 having domain @outlook.com.
  • UI changes for OAuth authentication.


Outlook.com Email Features (Supported & Not Supported)



Feature Point Status Description
Demo Version License Supported 100 items of email & 25 items of contact, calendar, document
Date Filter Supported From - To supported [Mails - Creation date]
Folder Structure Supported Original Structure Maintained
Max Path Length Supported 250
Max File Name Length Supported 50
Max Folder Name Length Supported 50
Maximum PST file Size Supported user can split PST int 10,20,30,40 GB
If PST file cross limit, then new PST will get created and data will be stored in new PST.
PST file Name Supported Default file will be created with “user email address.pst” and in case of crossing limit file will be created with incremental counter.
Mails
Special Characters / Foreign Language Folder Names Supported
Special Characters / Foreign Language Names For Email body, subject and attachment names Supported
Attachments Supported 33 MB tested
To, CC, Bcc Supported
Date & Time Retention Supported
Default Folder Mapping Supported
Read/Unread Status Supported
Conversation Thread Supported
Mail Body Format Supported
HTML Body Supported
Plain Body Supported
Inline Images Supported
Embedded Attachment Supported
All Mails folder Not Supported
Deleted Items Not Supported Supported
Maximum Mail Size Supported 33 MB tested
Importance (High, Medium, Low) Supported
Follow-up Flag Supported
Encrypted Email Supported
Calendar Invitation Email Supported
Delivery receipt Supported
Read Receipt Supported
Archive Emails Supported
Report phishing emails Supported Moved to Junk-Email
Email Reactions Not supported
Forward emails as attachment Supported
Favorite folder Not Supported
Folder sharing and Permissions Not Supported
Snooze Supported Mail backup in the Snoozed folder and snooze time is not visible
Email Pin Not Supported
Rules Not Supported
Notes Not Supported
Junk Email Supported
RSS Feed
Category Not Supported
Delete After Backup Supported Once the email backup is complete on the user status screen, the dropdown menu displays the option ""Delete Backup items from source."" Clicking this option opens a pop-up where you must manually enter the word ""Delete"" to permanently erase the emails from the source account.
Network Drive Supported

Shortcomings and Limitations


Limitation Reason
All folders will be 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.


API

The application is using the Microsoft Graph API which a REST based API for interacting with Office 365, too

Microsoft Graph REST API v1.0 endpoint reference - Microsoft Graph v1.0

Objective for Migrating Outlook.com Account Contacts

As a User, I should be able to take back up of Outlook.com account Contacts into a PST file so that I can securely store my emails contacts locally and manage them effectively, including optionally deleting the source contacts after backup.



Pre-Requisites for Contacts



  • Public project should be created on Azure portal (Applicable for SysTools Domain).
  • Free Space required on the End-User server for smooth backup process.
  • Delegate Scopes should be added in azure project
  • User Email Id is required for authentication.
  • Scopes (Delegated)
    • https://graph.microsoft.com/Contacts.Read - For Read and Delete
    • offline_access - To get the refresh token that can be used to get new access tokens in the future.
    • openid - The openid scope is the core scope used in OpenID Connect (OIDC), a protocol that builds on OAuth 2.0 for authentication. Application needs to authenticate a user and retrieve user identity information (e.g., their username, email, etc.), the openid scope is necessary.
    • profile - The profile scope requests permission to access the basic profile information(name, given_name, family_name,picture,locale) of the user from the identity provider (such as Google or Microsoft). This typically includes attributes like the user's name, profile picture, and locale.
    • email - The email scope allows the client application to request access to the email address of the authenticated user.

Outlook.com Contacts Features (Supported & Not Supported)

Feature Point (Supported) Status Description
Email Addresses Supported Only 3 emails will be allow.
Phone
  • Home
  • Work
  • Mobile
 Supported For Home and Work only 2 number will be allowed.
For Mobile only 1 number will be allowed.
Other
  • Organization Main
  • Pager
  • Other
  • Home Fax
  • Business Fax
  • Other Fax
  • Assistant Phone
  • Callback phone
  • Radio Phone
  • Telex
  • TTY
 Not Supported We do not get these properties from the Graph API.
IM Address (Chat) Supported
Work
  • Job title
  • Company
  • Department
 Supported
Note Supported
Profile Photo Supported
Personal Info
  • First Name
  • Last Name
  • Suffix
  • Prefix
    		•  Supported
    Personal Info*
    • YomiGivenName
    • YomiSurname
    • YomiCompanyName
    		 Supported Added in contact notes
    Address
    • Business
    • Home
    • Other
    		 Supported
    Other:
    • Nick Name
    • Birthday
    • Significant Other
    		 Supported
    Other:
    • Anniversary
    • Personal Web Page
    		 Not Supported
    Foreign Language Contact Name Supported
    Foreign Language Email Address Supported
    Foreign Language in Contact Body Supported
    Delta Backup Supported
    Group Contact Not Supported
    Frequent Contacts Not Supported
    Directory Contacts, Duplicates Not Supported
    Delegate Contacts Not Supported
    Linked Contact Not Supported
    Deleted contact Not Supported
    Favorites Not Supported
    Delete After Backup Supported Root folder is not visible in the source screen so that folder also proceed in deletion operation.

    Once the contact backup is complete on the user status screen, the dropdown menu displays the option ""Delete

    Backed up item from source."" Clicking this option opens a pop-up where you must manually enter the word ""Delete"" to permanently erase the emails from the source account.
    Network Drive Supported

    Shortcomings and Limitations



    Limitation Reason
    All folders will be 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.
    API

    The application is using the Microsoft Graph API which a REST based API for interacting with Office 365, too

    Microsoft Graph REST API v1.0 endpoint reference - Microsoft Graph v1.0

    Objective for Migrating Outlook.com Calendars

    As a User, I should be able to take back up of Outlook.com account Calendars into a PST file so that I can securely store my calendar locally and manage them effectively, including optionally deleting the source calendar after backup.



    Pre-Requisites
    • Public project should be created on Azure portal (Applicable for SysTools Domain).
    • Required Free Space on End-User Server for Optimal Backup Performance.
    • Delegate Scopes should be added in azure project
    • User Email Id is required for authentication.
    • Scopes (Delegated)
      • Calendar Read - https://graph.microsoft.com/Calendars.Read
      • Calendar Deletion - https://graph.microsoft.com/Calendars.ReadWrite
      • offline_access - To get the refresh token that can be used to get new access tokens in the future.
      • openid - The openid scope is the core scope used in OpenID Connect (OIDC), a protocol that builds on OAuth 2.0 for authentication. Application needs to authenticate a user and retrieve user identity information (e.g., their username, email, etc.), the openid scope is necessary.
      • profile - The profile scope requests permission to access the basic profile information(name, given_name, family_name,picture,locale) of the user from the identity provider (such as Google or Microsoft). This typically includes attributes like the user's name, profile picture, and locale.
      • email - The email scope allows the client application to request access to the email address of the authenticated user.


    Outlook.com Calendar Features (Supported & Not Supported)


    Feature Point (Supported) Status Description
    Free Trial Version Supported In Free Trial End User can Backup 25 Calendar.
    Date Filter Supported From - To Calendar - Event Start Date]
    Maximum PST file Size Supported user can split PST int 10,20,30,40 GB
    If PST file cross limit then new PST will get created and data will be stored in new PST.
    PST file Name Supported default file will be created with “user email address.pst” and in case of crossing limit file will be created with incremental counter.
    Calendar
    Special Characters / Foreign Language in Calendar Subject & Body Supported
    Special Characters / Foreign Language in Calendar Folder Name Supported
    Recurrence Supported
    Custom Recurrence Supported
    Meeting Link Supported Visible on Outlook Version 10 & above
    Attendees Supported
    Reminder Supported will be supported for future events.
    Time Zone Mapping Supported
    All Day Event Supported
    Description Supported
    Meeting Response Not Supported
    Status Supported
    Visibility Supported
    Future Events Supported The date range will be +1 year from the current date.
    Resources Supported
    Hidden Calendars Not Supported
    Reminders Calendar Folder Not Supported
    Tasks Calendar Folder Not Supported
    Deleted Item Not Supported
    Birthday Calendar Folder Not Supported
    Holiday Calendar Folder Not Supported
    Subscribed Calendars Not Supported
    Shared Calendar/Shared Calendar Folder Not supported
    Private Supported
    Inline Attachments Supported Visible on Outlook v10, 13, 16 & 19.
    Event Colour Not supported
    Folder Name Having Special Characters / \ : * ? “ < >| Supported
    Categories Supported
    Scheduling Assistant Supported
    Location Supported
    In-Person Supported Event without skype meeting select and with location consider as an In-Person event
    Event charm icons Not Supported calendar events will be backup without Charm icon property
    Scheduling Poll Not Supported
    Organizer Supported
    Skype Meeting Supported Meeting Link is backup Properly
    Network Drive Supported
    Shortcomings and Limitations


    Limitation Reason
    All folders will be 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.
    API

    The application is using the Microsoft Graph API which a REST based API for interacting with Office 365, too

    Microsoft Graph REST API v1.0 endpoint reference - Microsoft Graph v1.0

    Objective for Migrating Outlook.com OneDrive Items

    As a User, I should be able to take back up of Outlook.com account OneDrive so that I can securely store my OneDrive documents locally and manage them effectively, including optionally deleting the source Document after backup.



    Pre-Requisites for Migrating Outlook.com OneDrive


    • Public project should be created on Azure portal (Applicable for SysTools Domain).
    • Required Free Space on End-User Server for Optimal Backup Performance.
    • Delegate Scopes should be added in azure project
    • User Email Id is required for authentication.
    • Scopes (Delegated)
      • Document Read - https://graph.microsoft.com/Files.Read.All
      • Document Delete - https://graph.microsoft.com/Files.ReadWrite.All
      • offline_access - To get the refresh token that can be used to get new access tokens in the future.
      • openid - The openid scope is the core scope used in OpenID Connect (OIDC), a protocol that builds on OAuth 2.0 for authentication. Application needs to authenticate a user and retrieve user identity information (e.g., their username, email, etc.), the openid scope is necessary.
      • profile - The profile scope requests permission to access the basic profile information(name, given_name, family_name,picture,locale) of the user from the identity provider (such as Google or Microsoft). This typically includes attributes like the user's name, profile picture, and locale.
      • email - The email scope allows the client application to request access to the email address of the authenticated user.


    Outlook.com OneDrive Features (Supported & Not Supported)

    Feature Point (Supported) Status Description
    Free Trial Version Supported 25 Items of Document is backup in Free Trial version
    Date Filter Supported From - [Document - Modified]
    Document
    File Versions Not supported
    File Timestamps Not Supported
    Recycle bin Not supported
    Shared with me Not Supported
    Folder Structure supported
    Maximum File Name Length Supported 100 character supported if name more than 100 character will be trim after 100 character
    Maximum Folder Path Length Supported 200 character will be supported, after that hierarchy will be split to root level.
    Office 365 has 400 character limit for Document path
    Maximum Folder Length Supported 100 character will be supported, after that hierarchy will be split to root level.
    Special Characters / Foreign Language Names Supported Yes, Followed by windows system configuration. [Which are not supported are replaced with '_']
    File/Folder Name Existing conflicts Supported Yes, It Creates with incremental counter.
    Empty files (0 Size) Supported
    Delta Migration Supported Same file will be updated.
    Permissions Not Supported
    Maximum Document Size Supported 100 GB
    OneNote Not Supported
    Delta Backup Supported New Items will backup from selected folder
    Retry fail Backup Supported
    Re run Full Backup Supported
    Delete After Backup Supported Moved to the recycle bin of source account
    Network Drive Supported
    Shortcomings and Limitations

    Limitation Reason
    All folders will be 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.
    API

    The application is using the Microsoft Graph API which a REST based API for interacting with Office 365, too

    Microsoft Graph REST API v1.0 endpoint reference - Microsoft Graph v1.0

    Download Windows Version Download

    Download Mac Verison Download