It would be better if providing config files to jobs was as clean as providing credentials.

When I create a "Credentials Parameter", I only have to specify the stored principal from the credential store. My script uses the parameter as an opaque value. It might be a GUID, but I don't need to know that.

Providing managed files to jobs is not as convenient as this. I want to have the ability to add a "File ID Parameter" (can't use "File Parameter", as that already exists). I would just select the particular managed file from a dropdown, and my script would use the value opaquely, just like a credentials parameter.

I know I can create a managed file and override the guid value to use a more mnemonic value, but this is still a maintenance issue. Having a hardcoded string in the script to specify the file name is just not optimal. I suppose I could instead provide the id value as a parameter, but that still doesn't eliminate the implicit indirection to the managed file.