Bicep Deployment Script Task "Azure PowerShell" container instance is not able to find helper JSON path

[pratyaksh1302]

Bicep version
Bicep CLI version 0.17.1

Describe the bug
As a part of managing Azure AD objects automation using Deployment scripts as illustrated in the article-> https://learn.microsoft.com/en-us/samples/azure/azure-quickstart-templates/deployment-script-azcli-graph-azure-ad/

We developed PowerShell script which create Azure AD Users, Groups and were trying to load inputs from a JSON file which containers the configuration related to AD Users and Groups however when we deploy it using deployment script, the container is not able to find the path of helper JSON file using in the PowerShell script. This is not an expected behavior.

To Reproduce

1. Develop PowerShell Script
2. Script uses input.json to handle configurations related to Users and Groups
3. Deploy using Bicep deployment script using Azure PowerShell task.
4. Unable to find the path of the input.json

Tried using existing storage account and save this input.json in the existing storage account and referencing it in script did not worked.

Additional context
Hardcoding the JSON input in the PowerShell script and deploy using Deployment script worked as expected but using a json file doesn't work.

Could you please suggest an alternative for this problem?

Thanks,
Prat

[jeskew]

The Microsoft.Resources/deploymentScripts resource runs in an isolated container onto which your script will be copied. You can refer to other files, but you need to include a URL to such files in the supportingScriptUris property (as described here) so that those auxiliary files can be copied onto the same container before the script is run.