An Azure NoSQL database service for app development.
Hello !
Thank you for posting on MS Learn Q&A.
I had a similar issue before and this usually does not mean the whole Cosmos DB account is corrupted. I think it is more likely the dropped collections were deleted successfully and now you need either to a restore to recover the old version or to recreate the collections and indexes correctly.
For Azure Cosmos DB, whether you can restore a previous version depends on your backup mode. If the account uses continuous backup and Azure supports point in time restore within the retention window.
If it uses periodic backup, restore is typically done by Azure support from available snapshots rather than self service.
If your issue is specifically that index recreation fails you need to verify whether the failing indexes are unique indexes on Cosmos DB for MongoDB with continuous backup and in that case, you may need to restore the original collection or recreate the collection first and define the unique indexes at creation time.