Access to <random> in templates

Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

In the azure-arm docs, there is a long list of resources that are all named with a shared suffix. In my deployment, I need to create other temporary resources, and I'd like them to share the same suffix so that it's obvious they are part of this build, if it fails and leaves debris behind.

Use Case(s)

Packer builds with additional dependencies - in my case, an installer that won't complete without a SQL server database available, so I want to make a "mock" database in Azure SQL for the duration of the build.

Potential configuration

{{  .random }}

Potential References

Review the azure-arm documentation and search existing feature requests first; the issue proposes exposing a shared template value as {{ .random }}. Confirm the intended behavior for Packer builds with temporary Azure SQL dependencies, with completion meaning templates can reuse the same suffix across resources.