Integration service to Outlook 365 connection

We are in need of using Outlook 365 in Integration Services of UiPath to trigger processes by email receiving. In order to get service account connecting to Outlook 365, we need to have our registered application in Azure to meet the following requirements by UiPath documentation:

You must configure the application as a Multitenant application.

You must configure a Web Redirect URI. The Redirect URI (or callback URL) for your OAuth 2.0 application is https://cloud.uipath.com/provisioning_/callback.

You must set up delegated permissions. For more information, see Permissions in Microsoft’s official documentation.

Our IT doesn’t agree to create a multiTenant application. My questions is: Why do we have to use MultiTenant application to connect to Outlook 365?

@l.wang,

  1. Access to Multiple Tenants: Multi-tenancy allows an application to serve multiple customers (tenants) while keeping their data isolated. In the context of UiPath and Outlook 365 integration, this means your application can potentially access emails from multiple organizations or tenants.
  2. OAuth 2.0 Authorization Flow: OAuth 2.0 is the industry-standard protocol for authorization. When you integrate with Outlook 365, you’re essentially asking for permission to access someone’s emails. The multi-tenant configuration allows for a flexible OAuth flow where users from different organizations can grant access to their email accounts.
  3. Flexibility and Scalability: By creating a multi-tenant application, you’re setting up your integration to be flexible and scalable. It means your integration can potentially serve a broader range of users and organizations without needing individual setups for each. This is particularly useful if you’re planning to deploy your automation solution in environments where there are multiple organizations involved, such as in a consulting scenario or a shared services environment.
  4. Consistency and Ease of Management: Using a multi-tenant application model provides consistency in managing access across different organizations. It simplifies administration and maintenance because you’re dealing with a single application registration rather than managing multiple individual app registrations for each tenant.

While multi-tenancy offers these benefits, it’s understandable that your IT department might have concerns. They might worry about security, compliance, or other factors specific to your organization. It’s essential to address these concerns and find a solution that balances the requirements of your automation project with the security and compliance needs of your organization.

Generated by LLM but verified by expert.

Thanks,
Ashok :slight_smile:

Thank you very much, Ashok!

1 Like

@l.wang,

Glad I’m able to help you. Please Mark my answer as solution so it will be helpful to other community members.

Thanks,
Ashok :slightly_smiling_face:

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