Thanks for getting in touch! As variable sets are designed to be project-agnostic so you can apply them to any project, these variables cannot be scoped to project-specific deployment steps. Scoping to steps would have to be done with project variables, like you’ve mentioned.
If you have lots of variables in a set that you’d like to move over, we have a great example PowerShell script available to make the move a bit easier and quicker. From there you can then scope them to your deployment steps as needed.
I hope this helps! Don’t hesitate to reach out if you have any further questions.
One of the biggest benefits of variable sets I found is it brings clarity and seperation of concern to variable setup, especially when you are going through hundreds of variables. Allow it to be scopes to specific steps of a project would fulfill that purpose properly.
Thanks for following up and for sharing your suggestion. Unfortunately however, I would have to say implementing this functionality isn’t be something we could consider. Since variable sets are designed to be shared amongst multiple projects, allowing variables within a set to be scoped to project-specific deployment steps doesn’t fit within the functionality designed for them.
Sorry it’s not better news. Don’t hesitate to reach out if you have any further questions or concerns.