Dear community members,
I encountered an issue while attempting to move an Azure MongoDB Atlas resource from one resource group (RG) to another. Here are the details:
- Scenario: I created an Azure MongoDB Atlas service in the resource group named “xyz.”
- Objective: My goal was to move this MongoDB Atlas resource to a different resource group called “abc.”
- Process: I followed the regular procedure by initiating the move operation through the Azure portal.
- Error: After approximately 30 minutes, I received an uninformative error message labeled as “BadRequest.” The error message advised me to retry the operation or contact support.
- Resource Movement Status: Despite the error, the resource movement process appeared to be stuck in a perpetual “under process” state, even though no actual progress was being made.
- Impact: As a result, I had to wait for approximately 4 hours until the movement operation was finally canceled. During this time, I was unable to move other resources due to the ongoing background process associated with this MongoDB Atlas SaaS resource.
I would greatly appreciate any insights or guidance on resolving this issue. Has anyone else encountered a similar situation, and if so, how did you address it?