@Shelly R This scenario is covered in this article: VM Managed Disks, Resource Locks, and Failed Backup Snapshot Cleanups
Originally, when you enabled Azure Backup for a VM, it would create the (hidden) RestorePointCollections objects within the Resource Group where the VM itself was contained.
That created the issue with the whole Resource Lock scenario. So, the Azure Backup team changed that behavior, and now we have a separate resource group different than the resource group of the VM to store restore point collections.
And so, my current understanding is, you should be able to apply Resource Locks to the VM/its Resource Group, as long as you don’t apply it on the Resource Group that is auto-created to store the Restore Point Collections.
Hope that clarifies. Please let us know if there are any questions you may have.
------------------------------------------------------------------------------------------------------------------------------
Please do not forget to "Accept the answer" and "Up-Vote" wherever the information provided helps you to help others in the community.