Designing and Implementing Microsoft DevOps Solutions (AZ-400)

When a resource is moved to a different resource group within Azure, it retains the permissions that were assigned to it in the original group. This means that any role-based access control (RBAC) permissions that were granted previously continue to apply to that resource after the move.

The principle behind this is that Azure RBAC is applied at the resource level, so the unique permissions set on that resource remain intact regardless of the resource group's RBAC settings. This ensures that users or groups who had access to the resource before its relocation retain that access when the resource is moved, preventing unintentional access loss.

Understanding this behavior is vital for managing access controls effectively, especially in scenarios where resources are frequently moved between groups for organizational or management purposes. It helps ensure that access management remains consistent and predictable, allowing administrators to plan accordingly when reorganizing resources.