We're currently using Power Automate to manage data that exists in Dataverse tables that are part of the same tenant as the flows. Data access is typically done using the native Dataverse connection/connectors.
We're planning on moving some of the tables to a different Dataverse tenant, and we'd like to know what the most efficient way of managing access to these tables would be. Currently, I've come up with two options:
Create CRUD flows in the new tenant, and call those using the native Dataverse HTTP Request Action. This approach is almost certainly "okay", but feels very heavy-handed, as every table would need potentially four separate flows to handle the CRUD operations.
Use the Invoke an HTTP Request with Entra AD (preauthorized) and write queries using the Graph API. This feels more efficient, but I'm not terribly familiar with the Graph API. Does it have the ability to perform CRUD operations against any Dataverse table, or only the native tables? Are there any other limitations we should be aware of?
Are either of those two options the correct approach? Or is there any other alternative? In a perfect world we'd use the native Dataverse connector, but I can't find any way to create the connector to point to a different Dataverse tenant.
