Video tutorial

Watch this quick video to see the integration in action. It walks you through the end-to-end setup, including:

  • Installing the SSIS PowerPack
  • Configuring a secure connection to Outlook Mail (Office 365)
  • Working with Outlook Mail (Office 365) data directly inside SSIS
  • Exploring advanced API Source features
While this video uses the OData Connector as an example, the core concepts and setup process are exactly the same for the Outlook Mail (Office 365) Connector.

Video doesn't load? Watch this video on YouTube.

Ready to dive in? Download the product to jump right in, or follow the step-by-step guide below to see how it works.

Prerequisites

Before we begin, make sure the following prerequisites are met:

  1. SQL Server Data Tools (SSDT) designer installed for Visual Studio.
  2. SQL Server Integration Services Projects 2022+ Visual Studio extension installed.
  3. SSIS PowerPack is installed.

Send mail in SSIS

  1. Open Visual Studio and click Create a new project.

  2. Select Integration Services Project. Enter a name and location for your project, then click OK.

  3. From the SSIS Toolbox, drag and drop a Data Flow Task onto the Control Flow surface, and double-click it:

    Drag Data Flow Task onto Control Flow to use SSIS PowerPack Data Flow components

  4. Make sure you are in the Data Flow Task designer:

    Make sure you are in Data Flow designer in SSIS package

  5. Read the data from the source, using any desired source component. You can even make an API call using the ZappySys JSON/XML/API Source and read data from there. In this example, we will use an OLE DB Source component to read real-time data from a SQL Server database.

  6. From the SSIS Toolbox drag and drop API Destination (Predefined Templates) on the Data Flow Designer surface and connect source component with it, and double click to edit it.
    SSIS API Destination (Predefined Templates) - Drag and Drop

  7. Select New Connection to create a new connection:

    API Destination - Outlook Mail (Office 365)
    Read and write Microsoft Outlook Mail (Office 365) data effortlessly. Send, manage, and sync messages, attachments, and folders — almost no coding required.
    API Destination - Outlook Mail (Office 365)

  8. To configure the Outlook Mail (Office 365) connector, choose one of the following methods:

    • Choose from Popular Connector List: Select a pre-installed service directly from the dropdown menu.
    • Search Online: Use this to find and download a new connector file to your computer.
    • Use Saved/Downloaded File: Once the file is downloaded, browse your local drive to load it into the configuration.

    After that, just click Continue >>:

    Outlook Mail (Office 365)
    API Destination -

  9. Proceed with selecting the desired Authentication Type. Then select API Base URL (in most cases default one is the right one). Finally, fill in all the required parameters and set optional parameters if needed. You may press a link Steps to Configure which will help set certain parameters. More info is available in Authentication section.

    User Credentials

    Outlook Mail (Office 365) authentication

    Use delegated access (User Credentials) whenever you want to let a signed-in user work with their own resources or resources they can access. Whether it's an admin setting up policies for their entire organization or a user deleting an email in their inbox, all scenarios involving user actions should use delegated access. [API reference]

    Follow these simple steps below to create Microsoft Entra ID application with delegated access:

    WARNING: If you are planning to automate processes, we recommend that you use a Application Credentials authentication method. In case, you still need to use User Credentials, then make sure you use a system/generic account (e.g. automation@my-company.com). When you use a personal account which is tied to a specific employee profile and that employee leaves the company, the token may become invalid and any automated processes using that token will start to fail.
    1. Navigate to the Azure Portal and log in using your credentials.
    2. Access Microsoft Entra ID.

    3. Register a new application by going to App registrations and clicking on New registration button:

      Start new app registration in Microsoft Entra ID
      INFO: Find more information on how to register an application in Graph API reference.

    4. When configuration window opens, configure these fields:

      • Supported account type
        • Use Accounts in this organizational directory only, if you need access to data in your organization only.
      • Redirect URI:
        • Set the type to Public client/native (mobile & desktop).
        • Use https://zappysys.com/oauth as the URL.
      Register app in Microsoft Entra ID

    5. After registering the app, copy the Application (client) ID for later:

      Copy client ID of Microsoft Entra ID app

    6. Then copy OAuth authorization endpoint (v2) & OAuth token endpoint (v2) URLs to use later in the configuration:

      Copy Auth and Token URLs in Microsoft Entra ID app

    7. Now go to SSIS package or ODBC data source and use the copied values in User Credentials authentication configuration:

      • In the Authorization URL field paste the OAuth authorization endpoint (v2) URL value you copied in the previous step.
      • In the Token URL field paste the OAuth token endpoint (v2) URL value you copied in the previous step.
      • In the Client ID field paste the Application (client) ID value you copied in the previous step.
      • In the Permissions (Scope) field use the default or pick labeled permissions. [System] covers sign-in and refresh token. [User] is the signed-in user’s mailbox (use Mail.ReadBasic or Mail.Read for read-only). [Shared] adds shared or delegated mail folders. [Tenant] entries (User.ReadBasic.All, User.Read.All, Group.Read.All) are broad directory permissions that usually need an administrator to approve the app. The default includes User.ReadBasic.All for the Default User Id drop down; add User.Read.All only if you need full user profiles (not required for listing users).
        • offline_access, openid, profile, email
        • User.Read, Mail.ReadBasic, Mail.Read, Mail.ReadWrite, Mail.Send
        • Mail.Read.Shared, Mail.ReadBasic.Shared, Mail.ReadWrite.Shared, Mail.Send.Shared
        • User.ReadBasic.All, Group.Read.All (often admin consent; user drop down / group lookups)
        • User.Read.All (optional — full user profiles; broader than needed for user drop down)
        Admin consent note:
        • Token generation can still ask for admin approval, even when delegated scopes are listed in API permissions.
        • A Global Administrator can allow user consent for selected low-impact delegated permissions.
        • Broad mail or directory scopes such as Mail.ReadWrite, User.ReadBasic.All, User.Read.All, and Group.Read.All may still require admin consent.
        Settings: User consent settings (Entra ID > Enterprise apps > Consent and permissions > User consent settings). Docs: configure user consent, recommended settings.
    8. Press Generate Token button to generate Access and Refresh Tokens.

    9. Choose Default User Id from the drop down menu after token generation. This calls GET /users and requires User.ReadBasic.All in your token (included in the default scope list). Regenerate the token if you add or remove this scope later. Keep me for your own mailbox, or pick another user when accessing a shared or delegated mailbox. You can also type a user id or email manually if listing fails.

    10. Click Test Connection to confirm the connection is working.
    11. Done! Now you are ready to use the API Connector!

    API Connection Manager configuration

    Just perform these simple steps to finish authentication configuration:

    1. Set Authentication Type to User Credentials [OAuth]
    2. Optional step. Modify API Base URL if needed (in most cases default will work).
    3. Fill in all the required parameters and set optional parameters if needed.
    4. Press Generate Token button to generate the tokens.
    5. Finally, hit OK button:
    Outlook Mail (Office 365)
    User Credentials [OAuth]
    https://graph.microsoft.com/v1.0
    Required Parameters
    Authorization URL Fill-in the parameter...
    Token URL Fill-in the parameter...
    Application (client) ID Fill-in the parameter...
    Permissions (Scope) Fill-in the parameter...
    Return URL Fill-in the parameter...
    Optional Parameters
    Client Secret
    Refresh Token File Path
    Login Prompt Option
    Default User Id (Select after clicking **Generate Token**) me
    RetryMode RetryWhenStatusCodeMatch
    RetryStatusCodeList 429|503
    RetryCountMax 5
    RetryMultiplyWaitTime True
    ZappySys OAuth Connection
    Find full details in the Outlook Mail (Office 365) Connector authentication reference.
    Application Credentials

    Outlook Mail (Office 365) authentication

    Application-only access is broader and more powerful than delegated access (User Credentials), so you should only use app-only access where needed. Use it when: 1. The application needs to run in an automated way, without user input (for example, a daily script that checks emails from certain contacts and sends automated responses). 2. The application needs to access resources belonging to multiple different users (for example, a backup or data loss prevention app might need to retrieve messages from many different chat channels, each with different participants). 3. You find yourself tempted to store credentials locally and allow the app to sign in 'as' the user or admin. [API reference]

    Follow these simple steps below to create Microsoft Entra ID application with application access permissions.

    1. Navigate to the Azure Portal and log in using your credentials.
    2. Access Microsoft Entra ID.

    3. Register a new application by going to App registrations and clicking on New registration button:

      Start new app registration in Microsoft Entra ID
      INFO: Find more information on how to register an application in Graph API reference.

    4. When configuration window opens, configure these fields:

      • Supported account type
        • e.g. select Accounts in this organizational directory only if you need access to data in your organization only.
      • Redirect URI:
        • Set the type to Public client/native (mobile & desktop).
        • Leave the URL field empty.
      Register app in Microsoft Entra ID

    5. After registering the app, copy the Application (client) ID for later:

      Copy client ID of Microsoft Entra ID app

    6. Then copy OAuth authorization endpoint (v2) & OAuth token endpoint (v2) URLs:

      Copy Auth and Token URLs in Microsoft Entra ID app

    7. Continue and create Client secret:

      Add Client secret for Microsoft Entra ID app

    8. Then copy the Client secret for later steps:

      Copy Client secret

    9. Continue by adding permissions for the app by going to the API permissions section, and clicking on Add a permission:

      Start adding permissions to Microsoft Entra ID app

    10. Select Microsoft Graph:

      Select Graph API permissions for Microsoft Entra ID app

    11. Then choose Application permissions option:

      Select app permissions for Microsoft Entra ID app

    12. Continue by adding these Mail (Outlook) application permissions (for example Mail.Read, Mail.ReadWrite, or Mail.Send depending on your needs):

      Select Outlook Mail application scopes

    13. If you want the Default User Id drop down to list organization users (calls GET /users), repeat Add a permission and also add the User.Read.All application permission. Add Group.Read.All if you need group lookups. Search for User under Application permissions, select User.Read.All, then click Add permissions.

    14. Finish by clicking Add permissions button:

      Add permissions to Microsoft Entra ID app

    15. Now it's time to Grant admin consent for your application:

      Grant admin consent for Microsoft Entra ID app

    16. Confirm all the permissions are granted (Mail scopes plus User.Read.All when using the user drop down):

      Admin consent granted successfully in Entra ID

    17. Now go to SSIS package or ODBC data source and use the copied values in Application Credentials authentication configuration:

      • In the Token URL field paste the OAuth token endpoint (v2) URL value you copied in the previous step.
      • In the Client ID field paste the Application (client) ID value you copied in the previous step.
      • In the Client Secret field paste the Client secret value you copied in the previous step.
      • Choose Default User Id from the drop down menu (requires User.Read.All application permission and admin consent), or type a user id or email manually.
    18. Click Test Connection to confirm the connection is working.
    19. That's it! Now you can use the connector.

    API Connection Manager configuration

    Just perform these simple steps to finish authentication configuration:

    1. Set Authentication Type to Application Credentials [OAuth]
    2. Optional step. Modify API Base URL if needed (in most cases default will work).
    3. Fill in all the required parameters and set optional parameters if needed.
    4. Finally, hit OK button:
    Outlook Mail (Office 365)
    Application Credentials [OAuth]
    https://graph.microsoft.com/v1.0
    Required Parameters
    Token URL Fill-in the parameter...
    Application (client) ID Fill-in the parameter...
    Client Secret Fill-in the parameter...
    Scope Fill-in the parameter...
    Default User Id Fill-in the parameter...
    Optional Parameters
    RetryMode RetryWhenStatusCodeMatch
    RetryStatusCodeList 429|503
    RetryCountMax 5
    RetryMultiplyWaitTime True
    ZappySys OAuth Connection
    Find full details in the Outlook Mail (Office 365) Connector authentication reference.

  10. Select MyMessages table from the dropdown, then select Insert as operation, and hit Preview Data:

    API Destination - Outlook Mail (Office 365)
    Read and write Microsoft Outlook Mail (Office 365) data effortlessly. Send, manage, and sync messages, attachments, and folders — almost no coding required.
    Outlook Mail (Office 365)
    MyMessages
    Insert
    Required Parameters
    User ID or Email Fill-in the parameter...
    Optional Parameters
    DoNotOutputEmptyNestedProperty True
    DoNotOutputEmptyArrayProperty True
    RawOutputDataRowTemplate {}
    EnableRawOutputModeSingleRow True
    SSIS API Destination - Access table operation

  11. Finally, map the desired columns:

    API Destination - Outlook Mail (Office 365)
    Read and write Microsoft Outlook Mail (Office 365) data effortlessly. Send, manage, and sync messages, attachments, and folders — almost no coding required.
    API Destination - Outlook Mail (Office 365)

  12. That's it; we successfully configured the POST API Call. In a few clicks we configured the Outlook Mail (Office 365) API call using ZappySys Outlook Mail (Office 365) Connector

    Execute Package

Outlook Mail (Office 365) Connector actions

Need another use case? Pick the next Outlook Mail (Office 365) action in SSIS below.

Conclusion

You now know how to send mail in SSIS without writing complex code. Outlook Mail (Office 365) SSIS Connector handled pagination and authentication automatically.

Ready to get started? Download the trial or ping us via chat if you need help:

Download SSIS PowerPack
Chat with an Expert