Azure Cosmos DB approaches data consistency as a spectrum of choices. This approach includes more options than the two extremes of strong and eventual consistency. You can choose from five well-defined levels on the consistency spectrum.
With Cosmos DB any write into any region must be replicated and committed to all configured regions within the account.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels-tradeoffs

Scenario: App1 has the following data requirements:
Each instance will write data to a data store in the same availability zone as the instance.
Data written by any App1 instance must be visible to all App1 instances.
Azure Cosmos DB: Each partition across all the regions is replicated. Each region contains all the data partitions of an Azure Cosmos container and can serve reads as well as serve writes when multi-region writes is enabled.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/high-availability

Reference:
https://docs.microsoft.com/en-us/azure/api-management/transform-api