I'm a Dynamics 365 specialist trying to evaluate Matillion for extracting data and loading it into Snowflake.
Matillion has a Dynamics 365 Sales connector. Dynamics 365 Sales uses Dataverse as its underlying data store. Dataverse is also used by Dynamics 365 Marketing, Dynamics 365 Customer Service, Dynamics 365 Field Service and Dynamics 365 Project Operations.
Yet, none of these Dynamics 365 apps are mentioned in Matillion's documentation.
We're using Dynamics 365 Customer Service so we're running a proof-of-concept exercise to test the Matillion ETL Dynamics 365 Sales connector to see if we can use it to extract Customer Service data from Dataverse.
But is this a supported scenario? Will we hit licensing or support issues if we attempt something not documented by Matillion?
My hands on experience with Dynamics 365 (D365) is minimal at best but I think the answer about whether Matillion will work for most Dynamics 365 data scenarios is a yes. Take a look at this doc on the D365 query component: https://documentation.matillion.com/docs/2905604
Because it's a bit of a generic query component, I have a feeling it will work for the services you pointed out.
Generally speaking about Matillion connectors, most connectors are just an automation of API calls against the service it's calling. In your case Dynamics 365. So, what I would say is that if Dynamics 365 is exposed via a Rest API then the component in Matillion is likely using it. This also means that even if the Dynamics 365 connector does not work for all the other 365 services, you are not out of luck. One of Matillion's strong suits is being able to take nearly any exposed API and consume data from it using it's API Profiles or API Extract Profiles. This fundamentally makes ingesting from systems that Matillion doesn't necessarily have a component for very possible.