You may want to pose this question in DQ or PowerCenter discussion threads. From an MDM perspective, there will be no functionality needed in this regard and is only providing the data.

You can try to replicate the entire database instance as a whole rather than one record at a time. You can use Azure APIs to do the replication.

Migrate data from Oracle to Azure Cosmos DB Cassandra API using Blitzz | Microsoft Docs

Note: I haven't used the Blitzz API, but potentially you can use the snapshot migration of the database to replicate a snapshot of the Oracle data in Azure.

From what i could gather, Cosmos DB is a JSON document based storage, so if trying to replicate MDM datamodel if may need quite some design and effort on the backup storage, which is unwarranted.

instead you could leverage the BE apis and GET the json documents out of MDM and store it as-is in Cosmos DB.

Only problem remains on what basis the BEs can be synched to backup and how?

There are many ways you can try to publish the changes for ongoing basis

- One could be reuse existing Message trigger setup to generate C_REPOS_MQ_DATACHANGE table entry and instead of sending XMLs, create a ETL/ESB process that reads this table and fire a GET bes call for that ROWID

- Or if you dont have batch loads and simply rely on E360/BES calls, then use External calls like WriteBE, MergeBE and UnmergeBE to publish the BE json docs outside of MDM

-Sathiesh

I like to reiterate from my prev reply

-  Message trigger setup to generate C_REPOS_MQ_DATACHANGE table entry and instead of sending XMLs, create a ETL/ESB process that reads this table and fire a GET bes call for that ROWID

This will address both Batch and Realtime scenarios.

In my above suggestion pls feel free to replace ETL/ESB with Azure API/Data Factory whichever fits your needs