Configuring Microsoft Outlook as a Source
In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Microsoft Outlook option from the list of connectors. Click Next and you’ll be prompted to add your access.1. Add account access
Click the Microsoft Authentication button and sign in with the Microsoft account whose mailbox you want to sync. Microsoft asks you to allow Nekt to read your mail and your basic profile. Nekt only reads data: it never sends, changes or deletes emails. Both Microsoft 365 work or school accounts and personal Outlook.com accounts are supported.Reading mail is a permission that many organizations only let an administrator approve. If Microsoft shows a “Need admin approval” screen, ask your Microsoft 365 administrator to grant consent to Nekt for your organization, then authorize again.
- Initial sync date: Only emails received or changed on or after this date are synced.
-
Include SPAM and Trash: (Default:
false) When enabled, emails in the Junk Email and Deleted Items folders (and their subfolders) are also synced. When disabled, they are left out. -
Enable email attachments stream: (Default:
false) When enabled, the Email Attachments stream downloads the file attachments of every synced email and uploads them to a Nekt volume. This makes extractions significantly slower and heavier: each attachment is downloaded from Outlook and re-uploaded to Nekt. Only enable this if you need the email files stored in a Nekt volume. If you turn this option on for a source that already exists, the attachments of emails synced before only arrive after a Full Sync. - Attachments Volume: Nekt volume to upload email attachments to. Required when the email attachments stream is enabled.
2. Select streams
Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis.Tip: The stream can be found more easily by typing its name.Select the streams and click Next.
3. Configure data streams
Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.- Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
- Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
- Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
- Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
- Incremental (recommended for Email and Email Attachments): each run brings the emails received or changed since the previous run (read, flagged, categorized or moved to another folder), based on
last_modified_date_time. - Full table (used by Mail Folder): each run replaces the table with the current folder tree.
- Incremental (recommended for Email and Email Attachments): each run brings the emails received or changed since the previous run (read, flagged, categorized or moved to another folder), based on
4. Configure data source
Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:- Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
- Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
5. Check your new source
You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.Streams and Fields
Below you’ll find all available data streams from Microsoft Outlook and their corresponding fields. Every stream needs the permission to read mail that you grant when you authorize the source.Email
Every email of the mailbox, from all folders (Inbox, Sent Items, Drafts, Archive, your own folders and subfolders). Junk Email and Deleted Items are included only when Include SPAM and Trash is on. Sync is incremental on
last_modified_date_time: an email that is read, flagged, categorized or moved to another folder comes again with its new values.Key fields:Email Attachments
Email Attachments
Downloads the file attachments of the synced emails and uploads them to a Nekt volume, with one row per file. This stream only runs when Enable email attachments stream is on and a volume is selected; if the table is selected while the option is off, the run reports this table as failed and asks you to turn the option on or deselect it.
- Inline attachments (for example, images inside the body) are files too and are uploaded; use
is_inlineto tell them apart. - Attachments that are not files, such as an attached email, a calendar item or a link to a file in OneDrive or SharePoint, are not downloaded.
- When a file cannot be downloaded or uploaded, the email is retried on the next runs. On regular runs the run ends as a partial success; on the first load and on a Full Sync the run keeps every file it could save and shows a warning (it is reported as failed when no file could be saved or when an email is given up after 5 runs).
Mail Folder
Mail Folder
All mail folders of the mailbox, including subfolders and hidden folders, with their full path. The table is replaced on every run.Key fields:
Data Model
Use Cases for Data Analysis
Emails per folder. Join each email to the path of the folder that holds it.Example SQL (Trino / AWS Athena)
Example SQL (Trino / AWS Athena)
Example SQL (Trino / AWS Athena)
Example SQL (Trino / AWS Athena)
Replace schema and table names (
nekt_raw, microsoft_outlook_email, …) with the layer and table names you configured for the source.Implementation Notes
Extraction Behavior
- Email reads every folder in one ordered query by last change, page after page, up to the moment the run started. Changes made while the run is in progress are picked up by the next run.
- An email moved to another folder keeps its
id, so its row is updated with the newparent_folder_id. - Emails deleted permanently in Outlook are not removed from the table. With Include SPAM and Trash off, an email moved to Deleted Items keeps its last synced row.
- Microsoft limits how many requests a mailbox can receive. When it asks Nekt to slow down, the run waits as requested and continues, so large first syncs can take a while.
Attachments
- Files are downloaded one at a time, up to Outlook’s limit of 150 MB per file.
- Whenever an email changes (for example, it is read, flagged or moved to another folder), all its attachments are downloaded and uploaded again, replacing the files with the same names in the volume. Nothing is duplicated, but bulk actions such as “mark all as read” on a large folder make the next run longer. For large mailboxes, we recommend scheduling this source once a day.
- A Full Sync uploads every file again, under the same file names in the volume.
- If you turn on the attachments option for an existing source, run a Full Sync to also collect the attachments of emails synced before.
Skills for agents
Download Microsoft Outlook skills file
Microsoft Outlook connector documentation as plain markdown, for use in AI agent contexts.