Setting up MS Graph API authentication for Exchange Online

From September 2025 Microsoft is deprecating support for SMTP authentication for Exchange Online.

In TARGIT Management, to keep using Exchange Online as your email server, you will need to configure it with the MS Graph API protocol instead.

To do this, you will need to register MS Graph API as an application in your Azure Cloud environment to obtain the necessary IDs for the email server configuration. The IDs you require are:

  • Tenant ID
  • Application (client) ID
  • Client secret

Step-by-step, setting up MS Graph API application

  1. Login to your Azure portal at portal.azure.com
  2. Go to Microsoft Entra ID

     
  3. Go to App registrations and create a New registration

     
  4. Enter a suitable name and click Register

     
  5. Note the Application (client) ID and the Directory (tenant) ID. Copy these IDs to e.g., Notepad.
  6. Go to Certificates and Secrets and add a New client secret
  7. Enter a proper description and set an expiration date. We recommend the maximum expiration date. You will need to manually renew the client secret when, or before it expires.
    Note: If the client secret expires without being renewed, the email function in TARGIT will stop to work!
  8. At this point, as soon as the new client secret is created, remember to copy the Secret Value to your Notepad. You will not be able to go back and retrieve the value later.
  9. Go to API permissions, click Add a permission and select Microsoft Graph

     
  10. Select Application permissions and scroll down to the Mail.Send, Send mail as any user and click Add permissions


     
  11. Click Grant admin consent for <company name> and click Yes to grant consent

Use the Tenant ID, Application (client) ID and Client secret that you copied to Notepad to complete the configuration of the email server setup in the TARGIT Management client. See this article: Email server setup - Alerts and Notifications

 

Was this article helpful?
0 out of 0 found this helpful

Comments

2 comments
  • This is working fine, but we actually crash with the Microsoft Limits.
    Some jobs are producing E-Mail Outputs too fast, so that the API is throwing errors (500).

    In all Microsoft plans, we have a limit of 30 Mails per Minute.

    So, what could we do now?

    0
  • Hi Marc,

    Yes, you are right about the limitations on Microsoft 365 Exchange Online.

    Microsoft writes:
    "Exchange Online customers who need to send legitimate bulk commercial email (for example, customer newsletters) should use third-party providers that specialize in these services."

    "If an organization needs to send more emails to external recipients than the limits mentioned above, we recommend using Azure Communication Services email for bulk or high-volume emailing to external recipients."

    - https://learn.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits

    Best regards,

    Jesper da Silva Endelt

    0

Please sign in to leave a comment.