Right now, the "Match" and "notMatch" conditions only support # for digit placeholders and ? for letters. This is okay, but it would be much more useful to support regex expressions. This would needed for define complex naming policies and tagging standards.53 votes
If there are specific RegEx expressions needed, please leave them in the comments below. We will be investigating the feasibility. Thanks.
I am using Management groups and wanted to roll out multiple naming policy.
I have various clients hence thought of a consistent manner to support and organize Resource groups/Resources in a consistent way. i.e <Cleint>-<Prod/Dev>-RGP-<Name>.
So it would sort out like
but unfortunately found that match could not support a symbol which would represent letter or number in same symbol. Details can be seen in the closed feedback thread on the following page.
It would really help enforce a consistent naming convention.
Not sure how fast help can arrive from MS?11 votes
Thank you for the feedback. I will share this with the Policy team to see what options they currently have or if this is on their roadmap.
Is the blueprint available on GitHub at all?
I have taken the blueprint as a foundation for my "data centre in a box" template but, I have no way of seeing if there have been any changes to the MS provided one and if there are, what changes were made.
This is something we’d like to do, but haven’t committed to it yet.
In the meantime, you can always export any of the built-ins by creating one of them (which copies it into your tenant) and then exporting it with the Manage-AzureRMBlueprint script (https://www.powershellgallery.com/packages/Manage-AzureRMBlueprint/2.2).
- Don't see your idea?