geo redundant databases (azure SQL databases) will do the trick, but the data will only be made availble in case of a disaster at the primary DC
geo redundant databases (azure SQL databases) with read access will make these endpoints available to read out (you can use that for reporting services and so on)
do note that you can have up to 4 additional endpoints in different regions, but you will have to multiply the costs with the additonal endpoints.
if you are talking about IaaS databases, use the SQL replication mechanisms, with using geo redundant storage, this will not help you for application consistancy
for the webapps, in standard and premium, geo distributed deployments are supported. in this case put a load balancer in front of them:
- Traffic Manager can load balance on DNS
- Azure external load balancers can be used (with different rule sets)
- Application gateway can be used
Cheers Christophe
Kindly click Mark as Answer on the post that helps you, this can be beneficial to other community members reading the thread and Vote as Helpful
Azure Fanatic! www.cloudcrusader.com