Can I tag a resource, if that already has a resource lock?

Hi @Amit Kumar Srivastava ,

As explained here, you can set locks that prevent either deletions or modifications. In the portal, these locks are called Delete and Read-only. In the command line, these locks are called CanNotDelete and ReadOnly.

• CanNotDelete means authorized users can read and modify a resource, but they can't delete it.
• ReadOnly means authorized users can read a resource, but they can't delete or update it. Applying this lock is similar to restricting all authorized users to the permissions that the Reader role provides.

So, to answer your question,

• if a resource has already a Read-only resource lock in place, you can't apply a resource tag on that particular resource without removing the lock.
• if a resource has already a Delete resource lock in place, you can apply a resource tag on that particular resource without removing the lock.