M365 Move Mail not working

Hi,

I’m encountering a critical issue with the Move Email activity in the Microsoft 365 package (v3.5.10).

The activity executes without throwing an error, but it fails to move any emails. Despite the shared mailbox being enforced in both the Integration Service connection and the activity itself, debugging reveals that the sharedmailbox property of the Move Email activity is resolving as null .

Issue Summary:

  • Behavior: The BOT reads emails from the “RPA (before)” folder successfully, but the subsequent “Move Email” step does nothing and reports no exception.
  • Debugging Discovery: The Locals panel shows the shared mailbox account as null during the move operation, even when explicitly configured.
  • Attempted Fixes: I’ve already verified scopes, tested older package versions, tried different shared mailbox folders, and used various email types (with/without attachments).

Has anyone encountered a similar issue or found a workaround for this? I would appreciate any guidance or suggestions you might have.

Hi @piotrek11

This is a known bug in Microsoft 365 package where Move Email does not respect Shared Mailbox and resolves it as null at runtime.

The correct workaround is to use Move Mail Message with CurrentEmail.Id and explicitly enable Use Shared Mailbox.

If solution works for you please mark as solved

Thanks & Happy Automations

1 Like

hi @nishiijain2000

I cannot use CurrentEmail.MessageId because it returns a String , whereas the action requires an Office365Message object.

hi @piotrek11

Replace Move Email with HTTP Request activity using Microsoft Graph API directly. First, use Get Emails (Mail) to retrieve the message ID, then POST to https://graph.microsoft.com/v1.0/users/{sharedMailboxEmail}/messages/{messageId}/move with body {"destinationId": "{targetFolderId}"} —requires Mail.ReadWrite.Shared scope and obtains folder IDs via Get MailFolder. This bypasses activity bugs as Graph handles intra-mailbox moves reliably for shared mailboxes when using the /users/{id} endpoint.

1 Like

Please check :blush:

Hope it helps

Hi @arjun.shiroya

I am trying to move an email within the same shared mailbox.

Unfortunately, I cannot use Graph API HTTP requests. Due to internal policies, we are unable to use the M365 connector and must rely solely on the M365 Outlook connection within Integration Services. Consequently, the previously suggested method will not work for my setup.

@piotrek11
Please check

Cheers

@piotrek11

Create a dedicated Integration Service Outlook connection specifically for the shared mailbox in UiPath Automation Cloud > Integration Service > Connections > Add Connection > Microsoft Outlook 365, enabling “Use shared mailbox” and entering the full shared mailbox email address

Integration Service Scope (select the shared mailbox-specific connection)
├── Get Emails (Mail) → from “RPA (before)” folder → Emails (Office365Message array)
└── For Each CurrentEmail in Emails:
└── Move Email
├── Message: CurrentEmail
├── To email folder: Browse to “RPA (after)” folder using the connection’s folder picker
└── Use shared mailbox: Toggle ON (inherits from connection)

you can also refer to this:

@arjun.shiroya

I have everything just like you have mentioned - and it’s not working.

@piotrek11

Try this if it works for you - Forward Email to same mailbox folders and then Delete Email will clean original mail.

@piotrek11

You can use move outlook mail message activity

Hi @piotrek11

This is a known issue with Move Email (Microsoft 365) v3.5.10 when using shared mailboxes.

  • The activity runs without error but does nothing
  • At runtime, SharedMailbox becomes null, even if it’s configured
  • Reading emails works, but Move Email silently fails

Workaround:

  • Use Copy Email + Delete Email, or
  • Move the email using Graph API (HTTP Request)

It’s not a config or scope issue — it’s an activity limitation.

Hi @piotrek11 ,

If solution help you please mark as solution so it’s helps other too and thread will closed

Thanks

Hi Arjun.

The mistery was solved. The messages were moved by another users with access to the mailbox. They just forgot to tell me about it.

Thanks for letting us know, we had a ticket to investigate.