Orchestrator M365 Configuration

Hi, I have published a package which have 3 connections with Outlook365 but each one is different activity like one is Send Email and other is Get Email List, etc.

But the issue is when I configure this in Orchestrator, there is no indication which are which connection.

Is there any way for the activity names will be shown so I can correctly configure?

Thanks!

Hello @biw_nunticha

Welcome to the Community!

Steps I got for you from LLM:

  1. Use Descriptive Connection Names in Integration Service

When creating connections in Automation Cloud > Integration Service, name them clearly:

  • Outlook_SendEmail_Conn
  • Outlook_GetEmailList_Conn
  • Outlook_ReadInbox_Conn

These names will appear in Orchestrator, helping you match them correctly.

  1. Use Reference as in Studio

In each Use Outlook 365 activity, set the Reference as field to something meaningful:

  • "SendEmailConn"
  • "GetEmailListConn"

This helps internally in Studio and logs, though it won’t show in Orchestrator UI.

  1. Document Connection Mapping

Include a simple table in your library documentation:

Activity Name Reference As Expected Connection Name
Send Email SendEmailConn Outlook_SendEmail_Conn
Get Email List GetEmailListConn Outlook_GetEmailList_Conn
Read Inbox ReadInboxConn Outlook_ReadInbox_Conn

Please try this and let us know the result.

If your issue is resolved kindly mark this as solution to close this case.

Happy Automation

@biw_nunticha,

Make sure you name your Integration Services connections distinctly to identify there nature or role.

I have checked in Integration Service and tried to create new connection but there is nowhere I can put name in my Integration Service connections.

The thing is I used to publish a process and it showed the activity name like this, which I remember at that time I changed the name of the activity so I tried to do the same but it doesn’t work.

Use Descriptive Connection Names

In Studio, name each connection clearly (e.g., Outlook_SendEmail, Outlook_GetEmails, etc.).
These names will appear in Orchestrator, helping you identify them.
Document Connection Usage

Maintain a simple mapping document or README with:
Outlook_SendEmail → Used in Send Outlook Mail activity
Outlook_GetEmails → Used in Get Mail activity
Use Separate Workflows (Optional)

Split the activities into separate workflows or packages if the confusion is too high.
Each workflow will then have only one connection, making it easier to manage.
Check Connection Usage in Studio

Open the project in Studio and check the Connection Name property in each activity to confirm which one is used.

Blockquote