problem moved at new suscription

Hello @Aurora Technologies sas - Welcome to Microsoft Q&A and thanks for reaching out.

There are some important steps to do before moving a resource. By verifying these conditions, you can avoid errors.

• The resources you want to move must support the move operation. For a list of which resources support move, see Move operation support for resources.
• Some services have specific limitations or requirements when moving resources. If you're moving any of the following services, check that guidance before moving.
  • If you're using Azure Stack Hub, you can't move resources between groups.
  • App Services move guidance
  • Azure DevOps Services move guidance
  • Classic deployment model move guidance - Classic Compute, Classic Storage, Classic Virtual Networks, and Cloud Services
  • Networking move guidance
  • Recovery Services move guidance
  • Virtual Machines move guidance
  • To move an Azure subscription to a new management group, see Move subscriptions.
• If you move a resource that has an Azure role assigned directly to the resource (or a child resource), the role assignment isn't moved and becomes orphaned. After the move, you must re-create the role assignment. Eventually, the orphaned role assignment is automatically removed, but we recommend removing the role assignment before the move.
• For information about how to manage role assignments, see List Azure role assignments and Assign Azure roles.
• The source and destination subscriptions must be active. If you have trouble enabling an account that has been disabled, create an Azure support request. Select Subscription Management for the issue type.
• The source and destination subscriptions must exist within the same Azure Active Directory tenant. To check that both subscriptions have the same tenant ID, use Azure PowerShell or Azure CLI.
• For Azure PowerShell, use:

(Get-AzSubscription -SubscriptionName <your-source-subscription>).TenantId
(Get-AzSubscription -SubscriptionName <your-destination-subscription>).TenantId

For Azure CLI, use:

az account show --subscription <your-source-subscription> --query tenantId
az account show --subscription <your-destination-subscription> --query tenantId

• If the tenant IDs for the source and destination subscriptions aren't the same, use the following methods to reconcile the tenant IDs:
  - Transfer ownership of an Azure subscription to another account
  - How to associate or add an Azure subscription to Azure Active Directory
• The destination subscription must be registered for the resource provider of the resource being moved. If not, you receive an error stating that the subscription is not registered for a resource type. You might see this error when moving a resource to a new subscription, but that subscription has never been used with that resource type.

For PowerShell, use the following commands to get the registration status:

Set-AzContext -Subscription <destination-subscription-name-or-id>
Get-AzResourceProvider -ListAvailable | Select-Object ProviderNamespace, RegistrationState

To register a resource provider, use:

Register-AzResourceProvider -ProviderNamespace Microsoft.Batch
For Azure CLI, use the following commands to get the registration status:

Azure CLI

az account set -s <destination-subscription-name-or-id>
az provider list --query "[].{Provider:namespace, Status:registrationState}" --out table

To register a resource provider, use:

Azure CLI

az provider register --namespace Microsoft.Batch

• The account moving the resources must have at least the following permissions:
  • Microsoft.Resources/subscriptions/resourceGroups/moveResources/action on the source resource group.
  • Microsoft.Resources/subscriptions/resourceGroups/write on the destination resource group.
• Before moving the resources, check the subscription quotas for the subscription you're moving the resources to. If moving the resources means the subscription will exceed its limits, you need to review whether you can request an increase in the quota. For a list of limits and how to request an increase, see Azure subscription and service limits, quotas, and constraints.
• For a move across subscriptions, the resource and its dependent resources must be located in the same resource group and they must be moved together. For example, a VM with managed disks would require the VM and the managed disks to be moved together, along with other dependent resources.
• If you're moving a resource to a new subscription, check to see whether the resource has any dependent resources, and whether they're located in the same resource group. If the resources aren't in the same resource group, check to see whether the resources can be combined into the same resource group. If so, bring all these resources into the same resource group by using a move operation across resource groups.

For more information regarding the same, please take a look at this doc: move-resource-group-and-subscription

Hope this helps. and please feel free to reach out if you have any further questions.

------------------------------------------------------------------

If the above response was helpful, please feel free to "Accept as Answer" and "Upvote" the same so it can be beneficial to the community.