Hi,
I will try to cover all of your questions:
1. Change tracking on F&O virtual tables is still a preview feature: https://learn.microsoft.com/dynamics365/fin-ops-core/dev-itpro/power-platform/track-changes-fin-ops-virtual-table
2. Every poll is a live query in F&O. Dataverse forwards each request to a custom F&O service, which runs it as a query on the data entity on the AOS and the F&O database. The good thing is that F&O exempts these calls from its own throttling (throttling happens with ODATA and custom end points), but that doesn't make them free. They compete with your users and batch jobs and will get slower when F&O is busy. The throttling you will hit comes from Dataverse, on your adapter user (6,000 requests and 20 minutes of execution time per 5 minutes, per web server). 120 tables every 10 seconds is already about 3,600 calls per 5 minutes before paging.
3. The delta link is Dataverse's own change tracking, with a token that comes from F&O itself. The initial load goes through the same route: the first call without a token is a full read of the table through F&O, 20M+ rows paged. Tokens are valid for 10 days by default, so after a longer outage you're looking at that full read again. Plan it as an event, not a retry. Change tracking requests also don't support $filter, so you always get the whole table.
What I would need to further help you:
- What does near-real-time mean for you: seconds, or a few minutes?
- What consumes the data in Azure SQL MI: reporting, an app, or downstream processes that act on the changes? For the last one you'd want change events rather than polling a copy.
- Is it one-way, or does anything need to flow back into D365?
For reporting alone, Link to Fabric on the F&O tables is the standard route, with latency in minutes: https://learn.microsoft.com/power-apps/maker/data-platform/fabric-link-plan-latency.
For the other scenarios the answer changes quite a bit.
Kind regards,
Patrick Mouwen