Hello @surabhikatiyar_adobe ,
The "_msm_moved" is created when a rollout action is triggered and content is being rolled out to a live copy where an identically named resource is already located.
I am able to reproduce the behavior as you have demonstrated above and looks like the components under the Page get renamed to _MSM_MOVED.
You can refer to the documentation[1] where the above is explained in detail.
By default, AEM uses conflict handlers to resolve any page conflicts that exist when rolling out content from a blueprint to a live copy.
In AEM, we have the Configuration "Day CQ WCM Rollout Manager" which handles the MSM Configurations as mentioned in below URL[1]
If We disable the Property "Handle conflict with manually created Pages" Under the Day CQ WCM Rollout Manager then in that case AEM will not handle the conflict and MSM_MOVED Nodes will not created.
But at the same time, If you manually deactivate conflict handling then AEM takes no action on any conflicting pages (non-conflicting pages are rolled out as expected) .
Just to further add, AEM does not give any indication that conflicts are being ignored as this behavior must be explicitly configured, so it is assumed that it is the required behavior.
[1]- https://experienceleague.adobe.com/docs/experience-manager-64/administering/introduction/msm-rollout...
Please do let me know if you need any further clarification.
- Sameer
