web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Welcome to the Power Platform Communities
The Next Big Bite | Aussie Classics & Starting Small with Clay Wesener | EP04
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Power Automate to conn...
Power Automate
Answered

Power Automate to connect to dataverse in different tenant

(1) ShareShare
ReportReport
Posted on by Emad_Gerges 30
Hi,
I want to develop a workflow on Environment A on Tenant 1 and  want to access table from Dataverse on Environment B on Azure Tenant 2
Should I use HTTP requests to call the API to read data form the Dataverse or there is another way.
I found some users talking about SPN(Client ID/Secret) to connect as this link: https://d365demystified.com/2022/08/09/authenticate-dataverse-connector-using-service-principal-in-a-power-automate-flow/
What is the best solution to achieve that?
 
Categories:
General topics
I have the same question (0)
  • Suggested answer
    Michael E. Gernaey Profile Picture
    Michael E. Gernaey 53,968 Moderator on at
    HI
     
    There is no real such thing as the "best solution".
     
    If I was, I'd have to first add the User with a license onto the target Dataverse.
    Then use HTTP(s) calls to get the data.
     
    Using an SPN for another environment is NOT the right call as that control will only work on the local environment not the other.
     
    Another way, yet people still need licenses, is to setup a Registered app that you Canvas App Calls, and then that gets the data and returns it, but again everyone needs a license.
     
    Simply use the first thing (Https Connector)
  • Suggested answer
    SaiRT14 Profile Picture
    SaiRT14 1,992 Super User 2025 Season 1 on at

    I suggest Solution-1 as best based on my experience:

    • Solution-1: If you prefer a simpler and more secure solution, the Service Principal (SPN) with the Dataverse connector is the best choice. This allows you to access Dataverse across tenants without needing to manage individual API requests, and it scales better for complex processes.

    • Soution-2: If you need full control over API calls, custom queries, or specialized OData filtering, then using HTTP requests via the Dataverse API might be more appropriate. However, it requires managing tokens and handling security manually.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Welcome to the Power Platform Communities
The Next Big Bite | Aussie Classics & Starting Small with Clay Wesener | EP04

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 274 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 175

#3
Haque Profile Picture

Haque 166

Last 30 days Overall leaderboard

Featured topics

Known issue with browser automation in Power Automate for Desktop on Google Chrome 146 and 147
Share your ideas and struggles with building Power Automate flows!
Survey: Power Automate mobile app
How to Ask for Help with Your Power Automate Workflow
Flows are not visible for users who sign in with their personal accounts
Start and wait for an approval action
Restore a deleted flow
List of actions cheat sheet for Power Automate Desktop
Welcome to the Power Automate forum!

Product updates

Microsoft Power Platform Community release plans