Graph Migration

Help Integration Service
1

We’re currently migrating our Outlook automation from the classic Outlook activities to Microsoft Graph API. In our existing process, each transaction is represented as a List, which we loop through and process accordingly.

However, with Graph API, the output is now a List. I wanted to check:

  • Can we directly use O365Message objects as transaction items throughout the process?
  • What are the key differences or limitations compared to MailMessage that we should be aware of?
  • Are there any known impacts on queueing, serialization, or data extraction when switching to O365Message?
  • Any best practices or recommendations for adapting existing workflows to this new structure?

Appreciate any insights or experiences from those who’ve already made this transition.

2

Hi, @robot94809

When migrating from MailMessage to O365Message in UiPath:

Use O365Message directly for Graph API workflows.

You cannot directly convert or cast MailMessage to O365Message.

O365Message is not serializable, so don’t queue whole messages; queue only needed fields.

Adjust your workflow for O365Message properties (e.g., item.Subject, item.Body).

Handle authentication, API limits, and errors from Graph API properly.

Treat O365Message as a different object type, not a drop-in replacement

3

@arjun.shiroya
Noted, thank you :smiling_face:

4

Actually, the Office365Message is serializable. Still agree that most often it makes sense to add only the needed information to queue.

5

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