When using a lock step in a Pipeline it is possible to name a globally defined resource and lock it. However, in order to use lock to institute concurrency within a job, Pipeline would need to create an implicit (ephemeral) resource that prevents other jobs from entering the defined lock step.

There has been some discussion about how this would be implemented to avoid name collisions among different jobs.