Start/Stop VMs V2 function ignores Resourcegroup

Question

Hello,

thanks to Microsoft, we have to migrate to Start/Stop VMs V2.
The setup seemed to be not that complicated.

But:
The given resource group is completely ignored. Without any errors and other feedback.

Behaviour:
Every machine within this subscription, except 2 VMs, is started, which is not intended.

Expected behaviour:
Every machine within this resource group is started, except 2 VMs.

   
{
    "Action": "start",
    "EnableClassic": false,
    "RequestScopes": {
      "ExcludedVMLists": [
        "/subscriptions/11111111-2222-3333-4444-555555555555/resourceGroups/DEFAULT-STORAGE-WESTEUROPE/providers/Microsoft.Compute/virtualMachines/VM01",
        "/subscriptions/11111111-2222-3333-4444-555555555555/resourceGroups/DEFAULT-STORAGE-WESTEUROPE/providers/Microsoft.Compute/virtualMachines/VM08"
      ],
      "ResourceGroups": [
        "/subscriptions/11111111-2222-3333-4444-555555555555/resourceGroups/Default-Storage-WestEurope/"
      ],
      "Subscriptions": [
        "/subscriptions/11111111-2222-3333-4444-555555555555/"
      ]
    }
  }

What's wrong?

Note: The resource paths are all directly copied from the Azure Portal resource properties. And yes, I have noticed, that sometimes the resource group is uppercase, sometimes lowercase. But that's how the resource paths are shown, not my idea.

Cheers