An option to protect the "Pause" action on clusters with 2FA would help to reduce the chance of accidental pausing of production systems.

Provide Peering support for "Classic" (Hub and Spoke) VNet Peering topology, either directly or via a NAT

Alerts can be configured to send to specific Atlas Users, but not Atlas Teams, which diminishes the value of setting up a team of users.

Currently there is no way to test how applications behave during maintenance apart from waiting for maintenance, the ability to force a rolling cluster restart as happens during maintenance would be great. The failover is a different process and affects primary mainly.

When Atlas is performing maintenances such as setting changes and OS reboots Alerts will be triggered. It would be helpful to have these Alerts be disabled so that it doesn't cause false alarms or so much noise that they are ignored.

A widget or calculator in the Atlas UI, where the user can see the projected carbon footprint of a deployment per year while they are configuring the deployment. And / or a live counter of the carbon Footprint for each deployment/project/org.

We have a need to rename our databases as we sync them over to Atlas. However, mongomirror doesn't support that. So that leaves us with mongodump and mongorestore but our databases are large enough that we can't take the outage window necessary to go down that path. When will mongomirror support renaming databases during the import process?

Currently is not possible to enforce any kind of password policy via Atlas UI.
Would be nice to let user define an expiration time and password policy that user should meet.

The Atlas API should include "Last Login Date" for the GET /orgs/{ORG-ID}/users endpoint.

We need more than 100 database users, and have had the limit raised for existing projects, but new projects require us to have the limit increased. There is no way for us to verify which projects have the default 100 database users and which ones have had the limit raised. It would also be nice to track the percentage or number of database users available as a metric.

Please enable security key (e.g. https://www.yubico.com/gb/product/yubikey-5c-nfc/) option for MFA. Ideally using FIDO2 protocol

Mongorestore allows for the number of concurrent insertion workers per collection to be increased using the --numInsertionWorkersPerCollection option.

However, this is not available for mongomirror -- while you can increase the number of collections copied in parallel (--numParallelCollections), there's no parameter surfaced to allow more inserts to be occurring at the same time over multiple threads within each collection.

|t would be helpful to have a parameter like this to use to increase parallelization in order to increase the speed of migrations of large collections.

Currently to search through logs we have to download them and search through each log. It would be helpful to have a log browser capability that would allow us to look through and search all logs from the Atlas portal interface.

a cluster has been in development for awhile .. but as new cluster are created within the project.. we'd like to change the cluster name ..

If I already have Cloud Manager backups, or can take an EBS snapshot, I want to be able to quickly Live Migrate this replica set to minimize migration time and load on my existing infrastructure.

Upload good tutorials in YouTube about connecting mongodb atlas with available three options.

Currently maintenance windows are defined per project. With multiple clusters in a project, maintenance will be performed at the very same time.

We would like to space out maintenance windows per cluster in the same project, to prevent replica set election on multiple clusters taking place simultaneously.