Microsoft 365 Email Input

OL Connect Professional Workflow
1

Hi,

I am trying to set up a Workflow that uses the Microsoft 365 Email plugin. My customer is unsure what is needed to be set up in Azure AD and how that is done.

I have sent them the link to the Workflow Users Guide where it discusses the plugin. Is there any documentation I can send them on what and how to set up the application in Azure AD?

Thanks,

TW

2

Here’s an internal article I wrote to explain the feature in more detail. This should get your customer’s IT department rolling: Microsoft 365 Input and Output.pdf (507.5 KB)

1 Like
3

Thanks @Phil!

This is exactly what the customer was looking for.

4

Hi @Phil,

I was working with the customer trying to get Azure configured for the Office 365 Plugin using the documentation you gave me. He is wondering if the application needs Read permissions for all mailboxes in their Tenant or is there a way to only give permissions to the mailbox for the 1 user account we are trying read mail from?

Thx,

TW

5

The task requires access to all mailboxes since it is designed to be able to pull emails dynamically from different accounts. We are planning on implementing an option that would allow the plugin to work with a single account as well, but that will not be available before the Fall release of Connect, at the earliest.

6

Phil do you now if this has been implemented ?

7

Yes, it was implemented in the 2022.1 release.

1 Like
8

Hi @Phil ,

My client is having issue on how to register OL Connect into their Microsoft Office 365. Do you have steps by steps guideline on this?

Thanks and Regards,
Janice

9

Dear All,

My client manage to register into their Microsoft Office 365, by followed this guideline (Upland RightAnswers | RightAnswers Self-Service Portal),

But Workflow encounter below error:

INFO : 09:10:02.742 [0002] Running script file (320 lines, 11038 bytes)
INFO : 09:10:02.795 [0002] GraphAPI > Application login to MSGraph API
ERROR: 09:10:03.192 [0002] Office365EmailInput encountered an error : Operation [“Login”] failed with response : AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app ‘26a51462-ebe0-41e3-a82a-a63d4e3ee86a’. Trace ID: 8cc91782-e319-486c-b5ee-f88745190600 Correlation ID: f13c6174-2e57-49b2-82d2-01481b9e0260 Timestamp: 2025-02-27 01:10:05Z (401)
WARN : 09:10:03.192 [0002] CredentialError: Operation [“Login”] failed with response : AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app ‘26a51462-ebe0-41e3-a82a-a63d4e3ee86a’. Trace ID: 8cc91782-e319-486c-b5ee-f88745190600 Correlation ID: f13c6174-2e57-49b2-82d2-01481b9e0260 Timestamp: 2025-02-27 01:10:05Z (401)
ERROR: 09:10:03.203 [0002] Microsoft 365 Email Input: W1603 : Plugin failed - 09:10:03 (elapsed time: 00:00:00.471)

Can help to advise, what will be the root cause of above error?

Thanks and Regards,
Janice

10

You are certain that you have applied the client secret’s value and not Secret ID?

The error below seems to come from Microsoft 365.

Operation ["Login"] failed with response : AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app '[...]'. Trace ID: [...] Correlation ID: [...] Timestamp: 2025-02-27 01:10:05Z (401)