Skip to main content

Sumo Logic Notifications By Microsoft

sumo-logic-notifications

Version: 1.0
Updated: Dec 04, 2024

Integration with Sumo Logic platform for monitors and Microsoft (Outlook) notification.

Actions

  • Assess Alert Status (Scheduled) - Periodically monitor status of a Sumo Logic alert and notify a Outlook user about an unresolved alert.

Sumo Logic Notifications By Microsoft configuration

  1. In the main Sumo Logic menu, select your username and then Preferences.
  2. From the preferences screen, in the section My Access Keys, click Add Access Key.
    sumo-logic-notifications
  3. Populate the name and click Create Key.
    sumo-logic-notifications
  4. Copy the Access ID and Access Key and store them (temporally) into a text editor.
    note

    They won't be available again once you close this screen.

  5. Click Done after you copied the Access ID and Access Key.
    sumo-logic-notifications

Register an application

Registering your application establishes a trust relationship between your app and the Microsoft identity platform. The trust is unidirectional: your app trusts the Microsoft identity platform, and not the other way around.

Follow these steps to create the app registration:

  1. Sign in to the Azure portal.
  2. If you have access to multiple tenants, use the Directory + subscription filter
    /microsoft-ews in the top menu to select the tenant in which you want to register an application.
  3. Search for and select the Azure Active Directory.
  4. Under Manage, select App registrations > New registration.
  5. Enter a Name for your application. Users of your app might see this name, and you can change it later.
  6. Select Register to complete the initial app registration.
  7. Don't enter anything for Redirect URI (optional).
    /microsoft-ews

When registration completes, the Azure portal displays the app registration's Overview pane, which includes its Application (client) ID. Also referred to as just client ID, this value uniquely identifies your application in the Microsoft identity platform.

The client ID as one aspect in validating the security tokens it receives from the identity platform.
/microsoft-ews

Add credentials

Credentials are used by confidential client applications that access an API. Examples of confidential clients are web apps, or service- and daemon-type applications. Credentials allow your application to authenticate as itself, requiring no interaction from a user at runtime.
You can add client secrets (a string) as credentials to your confidential client app registration.


/microsoft-ews

Add a client secret

The client secret, known also as an application password, is a string value of your app.

  1. Select your application in App registrations in the Azure portal.
  2. Select Certificates & secrets > New client secret.
  3. Add a description for your client secret.
  4. Select a duration.
  5. Click Add.
  6. Record the secret's value for use in your client application code - it's never displayed again after you leave this page.

Add permissions to API

  1. Select your application in App registrations in the Azure portal.
  2. Select API permissions > Add a permission.
  3. Delegated permissions are selected by default. Delegated permissions are appropriate for client apps that access an API as the signed-in user, and whose access should be restricted to the permissions you select in the next step.
  4. Application permissions are for service- or daemon-type applications that need to access API as themselves, without user interaction for sign-in or consent. Unless you've defined application roles for your API.
  5. Select Add a permission, and add the following permissions (as shown in the screenshot).
    /microsoft-ews

EWS API to be configured for these permissions

Applications are authorized to call APIs when they are granted permissions by users/admins as part of the consent process. The list of configured permissions should include all the permissions the application needs.

API / Permissions

Microsoft Graph (7)

  • Mail.Read
    • Type: Delegated
    • Description: Read user mail
    • Admin: -
  • Mail.Read
    • Type: Application
    • Description: Read mail in all mailboxes
    • Admin: Yes
  • Mail.Send
    • Type: Delegated
    • Description: Send mail as a user
    • Admin: Yes
  • Mail.Send
    • Type: Application
    • Description: Send mail as any user
    • Admin: Yes
  • User.ReadBasic.All
    • Type: Delegated
    • Description: Read basic profiles of all users
    • Admin: Yes
  • User.ReadBasic.All
    • Type: Application
    • Description: Read basic profiles of all users
    • Admin: Yes

Change Log

  • December 04, 2024 - First upload
Status
Legal
Privacy Statement
Terms of Use

Copyright © 2024 by Sumo Logic, Inc.