Save Draft in Shared Mailbox - Failed to Execute API with Microsoft Outlook 365

Help Integration Service
, , , ,
1

Hi Everyone

I’m finding alternative solution to save email as draft in Shared Mailbox instead the Primary account.
Found there’s one post in forum suggest to use the Send Email activity from UiPath.MicrosoftOffice365.Activities package. However, I’m getting the error as shown in screenshot when I add new connection.

My primary account is the RPA robot account. My shared mailbox is user’s shared mailbox.
When I done keyed in the credential of RPA robot account, UiPath prompt me the error shown in screenshot.

The user’s shared mailbox is granted “Send As” authorization only to the RPA robot account.

What could be the cause of fail to create the connection?

image
image676×356 42.4 KB

Cheers,
Gwen.

2

@Gwen

As per error looks like the account you are using is an individual account and not a enterprise account ..is that so?

If individual account then you cannot connect it thats a microsoft limitation

Cheers

3

Hi @Anil_G
I’m using enterprise account. Both RPA robot email and shared mailbox are enterprise account.

Is it because the primary account (Robot RPA email) does not grant with the authorization to access the Shared Mailbox? As it only granted with “Send As” permission to allow the primary account to be able to send on behalf of the shared mailbox.

So it couldn’t locate the mail folder from the outlook?

Like this screenshot below

image
image193×273 2.6 KB

Please correct me if I’m wrong.

Cheers

4

@Gwen

firs thing the account details or credentials you provide when making connection in orchestrator would be robot account and not shared account

when you see this error when using direct or enterprise account then you might have restrictions from your org to connect…

the shared mailbox comes into picture only when sending or receiving but not while establishing the connection

cheers

5

Hi @Anil_G

Yes, the connection is the robot account.

image
image373×623 18.2 KB

The connection was successfully established if I didn’t specify the shared mailbox.
If I specify the user’s shared mailbox or my work shared mailbox, it gives me the error.

image
image485×903 124 KB

I tried with my work email account, and specify my work shared mailbox, it managed to establish the connection.

image
image1364×348 48.2 KB

I also tried connecting my work email account with the user’s shared mailbox, it fails.

Perhaps like you mentioned - restrictions from my org to connect :thinking:?

6

@Gwen

Okay now its clear..o365 is different from outlook365 connection

And to use shared mailbox in outlook365 you need to have the shared mailbox setup ..inly sendas would not suffice

Cheers

1 Like
7

Hi @Anil_G

That’s great info! I’ll check with the org regarding the authorization.

Other than that, is there any other workaround to have the email saved as a draft in the shared mailbox (worst case, if the org only allows “Send As” permission)?

Cheers,
Gwen

8

@Gwen

then you might not be able to use integration services..if you use normal outlook then can save in draft and move it to shared box draft..but we need to check the feasibility also as this used to support previously but with latest upgrades I am not sure on outlook app

cheers

1 Like
9

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.