Thanks for posting your question in the Microsoft Q&A forum.
It seems that the deployment process lacks permissions to perform certain actions on the resource group or its linked scope.
Azure deployments often require permissions beyond just owning the resource group. review the Azure portal or use Azure CLI to verify the current role assignments for the user or service principal involved. checking and adjusting permissions at the subscription level, ensuring that the deployment process has sufficient permissions across all scopes where actions are required.
Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful