We will start with the Configure blade—when you click on it, you will see that it allows you to set both the tier and the pricing model of your database. This option is especially helpful when you want to improve the performance of your database; you can easily change the amount of DTU or vCores allocated for it, so it can work with queries much quicker.
As I mentioned before, configuring a single database will work for simpler scenarios, where you can easily monitor it and the performance requirements do not rapidly change. In all other cases, the better option is to use elastic pools.
When you go to the Geo-Replication blade, you will see a similar map to the one you saw when testing Azure Cosmos DB:
