"Native" Azure integration (Costing, Resource Groups)
I would love to do away with MongoDB CosmosDB on Azure - simply because
a) CosmosDB emulator is troublesome to install (for local development)
b) Limited MongoDB feature support
c) Difficulty getting Bulk inserts/upserts to work well in CosmosDB MongoDB (due to rate limiting and bugs with IsUpsert=true)
Currently we have 18 CosmosDB databases - nfortunately, the main barrier of entry for my organization in adopting Atlas is it's Azure integration - specifically:
a) Atlas resources are not visible/manageable via Azure Resource Groups - this makes our existing Azure DevOps practices/infrastructure as code obsolete for this (versus all our other resources being managed via Azure CLI
b) Major issue: Costing - our organization is still fairly new to cloud adoption - we've gotten over most adoption hurdles - but complicating it further by not having the costing aspects integrated with current cloud costing spreadsheets & reporting. In addition - this is also going to make this political and difficult to approve (we're a global organization).
Regarding (a) is it possible that you could integration MongoDB Atlas into your infrastructure as code posture using our Terraform provider? Or would Atlas be the only part of your stack using Terraform and that would be burdensome? We could explore introducing better integrations from Azure DevOps to MongoDB Atlas management over time--it's something we'd likely want to talk to you about for guidance in future.
Regarding (b) That makes sense: note that MongoDB Atlas does aim to provide easy to use billing visibility including at a glance rollups of Project-level spend within an Atlas Org: also this billing data is accessible through the Atlas API and can also be downloaded in CSV form for processing. Note as well that you can procure annualized subscriptions via the Azure marketplace. We would be happy to work with you to try to alleviate these challenges over time: many of our customers work through this including the political internal charge-back management, and we have resources that can help.