We are building a globally distributed application that will utilize Azure B2C a REST API to enrich the token. The application can be deployed in multiple Azure regions. I am trying to find the best approach to minimize latency between Azure B2C and the REST API.
The challenge that I am running into is that I don't know in which Azure B2C Region is running so I don't know in which Azure region to place the REST API's.
Let's assume that I establish an Azure B2C tenant in the US because that's where the majority of the users are located. Users can use Azure B2C from the US (unknown region) or from Europe (unknown region).
Use Case #1: US based user accesses Azure B2C. B2C calls the REST API. There's a potential for Azure B2C to be running on the West Coast while the application is in East.
- Should we place the REST API in multiple Azure Regions and use Azure Traffic Manager with a performance profile? We would have to replicate our additional claim/scope data to West, Central and East data centers.
- Will Azure B2C respect the DNS changes that ATM will make to route to a different API for performance and for DR reasons as well?
Use Case #2: European based user accesses Azure B2C. Is this request made to an Azure B2C instance running in the US since the tenant was established in the US?
- If this is the case then there would be no value to replicating our data to Europe since all requests would always be routed back to the US
Sorry about the long set of questions. I couldn't find reference material for globally Azure B2C implementations.