|
| 1 | +--- |
| 2 | +title: Sumo Logic Notifications By Microsoft |
| 3 | +description: '' |
| 4 | +--- |
| 5 | + |
| 6 | +import useBaseUrl from '@docusaurus/useBaseUrl'; |
| 7 | + |
| 8 | +<img src={useBaseUrl('/img/platform-services/automation-service/app-central/logos/sumo-logic-notifications.png')} alt="sumo-logic-notifications" width="100"/> |
| 9 | + |
| 10 | +***Version: 1.0 |
| 11 | +Updated: Dec 04, 2024*** |
| 12 | + |
| 13 | +Integration with Sumo Logic platform for monitors and Microsoft (Outlook) notification. |
| 14 | + |
| 15 | +## Actions |
| 16 | + |
| 17 | +* **Assess Alert Status** (*Scheduled*) - Periodically monitor status of a Sumo Logic alert and notify a Outlook user about an unresolved alert. |
| 18 | + |
| 19 | +## Sumo Logic Notifications By Microsoft configuration |
| 20 | + |
| 21 | +1. In the main Sumo Logic menu, select your username and then **Preferences**. |
| 22 | +2. From the preferences screen, in the section **My Access Keys **, click **Add Access Key **. < br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/sumo-logic-notifications-by-gmail/sumo-logic-notifications-by-gmail-2.png')} style={{border:'1px solid gray'}} alt="sumo-logic-notifications" width="600"/> |
| 23 | +3. Populate the name and click **Create Key **.< br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/sumo-logic-notifications-by-gmail/sumo-logic-notifications-by-gmail-3.png')} style={{border:'1px solid gray'}} alt="sumo-logic-notifications" width="400"/> |
| 24 | +4. Copy the **Access ID** and **Access Key** and store them (temporally) into a text editor. |
| 25 | + :::note |
| 26 | + They won't be available again once you close this screen. |
| 27 | + ::: |
| 28 | +5. Click **Done ** after you copied the Access ID and Access Key.< br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/sumo-logic-notifications/sumo-logic-notifications-4.png')} style={{border:'1px solid gray'}} alt="sumo-logic-notifications" width="400"/> |
| 29 | + |
| 30 | +### Register an application |
| 31 | + |
| 32 | +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. |
| 33 | + |
| 34 | +Follow these steps to create the app registration: |
| 35 | + |
| 36 | +1. Sign in to the [Azure portal](https://portal.azure.com/). |
| 37 | +2. If you have access to multiple tenants, use the Directory + subscription filter < br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/microsoft-ews/microsoft-ews-1.png')} style={{border:'1px solid gray'}} alt="/microsoft-ews" width="30"/> in the top menu to select the tenant in which you want to register an application. |
| 38 | +3. Search for and select the **Azure Active Directory**. |
| 39 | +4. Under **Manage**, select **App registrations > New registration**. |
| 40 | +5. Enter a Name for your application. Users of your app might see this name, and you can change it later. |
| 41 | +6. Select **Register** to complete the initial app registration. |
| 42 | +7. Don't enter anything for **Redirect URI (optional) **.< br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/microsoft-ews/microsoft-ews-2.png')} style={{border:'1px solid gray'}} alt="/microsoft-ews" width="800"/> |
| 43 | + |
| 44 | +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. |
| 45 | + |
| 46 | +The client ID as one aspect in validating the security tokens it receives from the identity platform.< br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/microsoft-ews/microsoft-ews-3.png')} style={{border:'1px solid gray'}} alt="/microsoft-ews" width="800"/> |
| 47 | + |
| 48 | +### Add credentials |
| 49 | + |
| 50 | +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. |
| 51 | +You can add client secrets (a string) as credentials to your confidential client app registration. |
| 52 | + |
| 53 | +< br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/microsoft-ews/microsoft-ews-4.png')} style={{border:'1px solid gray'}} alt="/microsoft-ews" width="800"/> |
| 54 | + |
| 55 | +### Add a client secret |
| 56 | + |
| 57 | +The client secret, known also as an application password, is a string value of your app. |
| 58 | + |
| 59 | +1. Select your application in **App registrations** in the Azure portal. |
| 60 | +2. Select **Certificates & secrets > New client secret**. |
| 61 | +3. Add a description for your client secret. |
| 62 | +4. Select a duration. |
| 63 | +5. Click **Add**. |
| 64 | +6. Record the secret's value for use in your client application code - it's never displayed again after you leave this page. |
| 65 | + |
| 66 | +### Add permissions to API |
| 67 | + |
| 68 | +1. Select your application in **App registrations** in the Azure portal. |
| 69 | +2. Select **API permissions > Add a permission**. |
| 70 | +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. |
| 71 | +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. |
| 72 | +5. Select **Add a permission **, and add the following permissions (as shown in the screenshot). < br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/sumo-logic-notifications-by-microsoft/sumo-logic-notifications-by-microsoft-1.png')} style={{border:'1px solid gray'}} alt="/microsoft-ews" width="800"/> |
| 73 | + |
| 74 | + |
| 75 | +#### EWS API to be configured for these permissions |
| 76 | + |
| 77 | +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. |
| 78 | + |
| 79 | +**API / Permissions** |
| 80 | + |
| 81 | +Microsoft Graph (7) |
| 82 | + |
| 83 | +* Mail.Read |
| 84 | + + Type: Delegated |
| 85 | + + Description: Read user mail |
| 86 | + + Admin: - |
| 87 | +* Mail.Read |
| 88 | + + Type: Application |
| 89 | + + Description: Read mail in all mailboxes |
| 90 | + + Admin: Yes |
| 91 | +* Mail.Send |
| 92 | + + Type: Delegated |
| 93 | + + Description: Send mail as a user |
| 94 | + + Admin: Yes |
| 95 | +* Mail.Send |
| 96 | + + Type: Application |
| 97 | + + Description: Send mail as any user |
| 98 | + + Admin: Yes |
| 99 | +* User.ReadBasic.All |
| 100 | + + Type: Delegated |
| 101 | + + Description: Read basic profiles of all users |
| 102 | + + Admin: Yes |
| 103 | +* User.ReadBasic.All |
| 104 | + + Type: Application |
| 105 | + + Description: Read basic profiles of all users |
| 106 | + + Admin: Yes |
| 107 | + |
| 108 | +## Change Log |
| 109 | +* December 04, 2024 - First upload |
0 commit comments