Thanks for getting in touch! You should be able to use a normal "Prompted Variable" defined in the Project for this. The idea is that:
You should be prompted for a value upon each time you deploy a release
We create a new deployment for every tenant
So in effect you should be prompted for this value when you create a deployment for any tenant, and you can provide the password appropriately.
However: I found a problem for your scenario. The UI only shows you a single prompt for a value - and then applies that single value to all the tenanted deployments created when you click the Deploy button.
I'm going to raise this with my team and figure out how we want to proceed from here.
In the meantime
You can still create the prompted variable, but just deploy to a single tenant at a time.
Thanks for keeping in touch! I've had a talk with my team, and we definitely want to do something to make this user experience better, but not just for prompted variable values. We have some similar issues when you are creating multiple tenanted deployments:
Are you blocked? I feel like there are some workable alternatives:
Put your passwords in Octopus - this is extremely common. The downside is if you update your passwords frequently. The upside is you'll remove the requirement for a human in the loop to enter the password on each deployment.
Use a prompted variable but deploy to one tenant at a time.
Use the Octopus API to kick off your deployments, pulling the password from your common store.