无法将云服务（扩展支持）移动到另一个资源组
我们在将云服务（扩展支持）从同一订阅中的 1 个资源组移动到另一个资源组时遇到问题。两个资源组都位于同一位置。
验证窗口中的错误代码是： { "code": "ResourceMoveNotSupported", "target": "/subscriptions/123456-xxxx-yyyy-zzzz-123456/resourceGroups/AAAAA-BBBBB-Migerated/providers/Microsoft.Compute/cloudServices/AAAAA-BBBBB" , "message": "资源类型不支持资源移动 'Microsoft.Compute/cloudServices'。” }
其他信息： 源资源组是在从云服务（经典）成功就地迁移到云服务（扩展支持）后自动创建的。现在我们需要将迁移创建的所有资源移回原来的资源组，即云服务（经典）之前所在的位置。云服务（经典）在迁移后自动删除。
我们从云服务（经典）迁移到云服务（扩展支持）的主要原因是能够在订阅之间移动，但即使在同一订阅内我们也无法移动它:(
有什么想法如何处理这个问题吗？
we have problem to move Cloud Service (Extended Support) from 1 resource group to another resource group in the same subscription. Both resource groups are in the same location.
Picture with status of the move validation
Error code in validation window is:
{ "code": "ResourceMoveNotSupported", "target": "/subscriptions/123456-xxxx-yyyy-zzzz-123456/resourceGroups/AAAAA-BBBBB-Migrated/providers/Microsoft.Compute/cloudServices/AAAAA-BBBBB",
"message": "Resource move is not supported for resource types
'Microsoft.Compute/cloudServices'." }
Additional information:
Source resource group was created automatically after successful in-place migration from Cloud Service (Classic) to Cloud Service (Extended Support). Now we need to move all resources created by migration back to the original resource group, where Cloud Service (Classic) was previously located. Cloud Service (Classic) was automatically deleted after migration.
The main reason why we migrated from Cloud Service (Classic) to Cloud Service (Extended Support) was ability to move between subscriptions, but we are unable to move it even inside the same subscription :(
Any ideas how to proceed with this problem?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
最佳做法是创建 Azure 支持票证。
这些类型的操作是 azure 的深层内部操作，这些失败的原因包括配置错误、失败的内部事务以及他们没有考虑的场景的直接错误。
注意：您可能需要一些时间和耐心才能从 Azure 支持获得所需的结果，因为这些类型的票证通常优先级较低。
Best course of action is to create an Azure Support Ticket.
These type of operations are deep internal to azure, and reasons why these fail range from config errors, failed internal transactions to straight up bugs for a scenario they did not consider.
Note: it might take some time and patience on your side to get the desired results reached from Azure support, as these type of tickets are usually low priority.
我们终于联系到了 Azure 支持。
不支持此举动:(
We finally managed to contact Azure Support.
This move is not supported :(