Thanks for reaching out. The transformations don’t support absolute paths, at least not on the right hand side. The right hand side is only file name of the config the transform is to be applied to. There are docs here, just in case you haven’t seen them yet.
There are other potential traps in this too. I assume you’re deploying an Azure Web App or Function? Do you then have multiple steps? If you are, this will work while you only have a single worker (there’s a built in one by default that Azure steps run on), but as soon as there a multiple there is no assurance they will run on the same worker. There is also no assurance that the worker won’t clean up files between steps. So assuming the paths will always be relative across these steps is brittle.
Is there data in the config file that you need separated for security purposes or something like that? Just trying to understand what’s driving the need for the separate packages.