@Mahammad Kanekallu (Contractor) Greetings!
On a high level we recommend using Azure Site Recovery to plan business continuity and disaster recovery (BCDR). However, your question is specific to Cosmos DB and Storage account.
For Cosmos DB: If your Cosmos DB account is set up for multi-region writes, you can initiate a failover to another region directly. This allows you to switch the active region to your secondary region without data loss.
Reference links: https://video2.skills-academy.com/en-us/azure/cosmos-db/nosql/how-to-multi-master?tabs=api-async
https://video2.skills-academy.com/en-us/azure/cosmos-db/distribute-data-globally
For Storage account: If your storage account is enabled with LRS, it replicates three copies of your storage account within a single datacenter. Although LRS protects your data against server rack and drive failures, it doesn't account for disasters such as fire or flooding within a datacenter. In the face of such disasters, all replicas of a storage account configured to use LRS might be lost or unrecoverable.
Suggestions: You will need to implement your own backup strategy. You can periodically copy data to another storage account in a different region using Azure Data Factory, AzCopy, or similar tools. In the event of a disaster, you can restore from these backups to a new storage account in the target region.
Geo-Redundant Storage (GRS):
If your storage account is configured with Geo-Redundant Storage (GRS), Azure automatically replicates your data to a secondary region. In case of a disaster, you can initiate a failover to access the data in that secondary region.
Note that this failover process will require some manual steps to access the data and update any applications using the storage account.
Hope this answers your question. Please write back to us if you have any further questions in this matter!
If the response helped, do "Accept Answer" and up-vote it