We have several Yaml pipelines using the same deployment environment. A new pipeline has just been created using Yaml that specifies the resource name (as well as the environment), as we want to deploy to one VM only within that environment. This is the first pipeline we have created that specifies the resource name explicitly. All previous ones deploy to the whole environment.

      displayName: Deploy
      environment: 
       name: 'NonProd'
       resourceName: 'Kermit'       
       resourceType: VirtualMachine

Since creating this pipeline, when running any of the other pipelines in the same environment, we are now asked to permit access to a resource before the deploy step can start. All other pipelines have been previously given permission to run in the NonProd environment.

I am struggling to understand what has changed to cause this to happen.

I am unable to find the resource that this message refers to. Therefore, I am unable to grant all current pipelines access, without running them individually. The message states Agent pool, but we have no agent pool with that name. I do know that environment 14 is the NonProd environment – but there is no resource with that name inside the environment either.

I can only assume that something has fundamentally changed in the NonProd environment, by running a pipeline that deploys only to one VM; and that the resource it is looking for is linked to that environment.

I would have hoped to have at least found the resource that the pipelines are now requiring access to.

I have tried looking for the resource in question both in the Environment and the Agent Pool. I have also tried using the graph API to locate the resource – to no avail.

Does anyone know what resource it is that the pipelines require access to – and if there a way to globally grant all pipelines access to this resource?