Stanley Merkx
My feedback
-
1 voteStanley Merkx
shared this idea
·
-
24 votesStanley Merkx
supported this idea
·
Stanley Merkx
commented
Please make ALL resources taggable.
I have recently implemented a policy to copy tag values from the resource group onto individual resources within the RG (See https://docs.microsoft.com/en-us/azure/governance/policy/concepts/definition-structure#policy-function-examples), but when a group contains resources that are not taggable, the policy is shown as non-compliant for that subscription.
-
12 votesStanley Merkx
commented
Similar problem between portal and Powershell: the portal (mostly) treats Tags as case insensitive, while manipulation of Tags from Powershell is case sensitive. Make your mind up about how to treat Tags and stick to it...
-
5 votesStanley Merkx
commented
Agreed, but Get-AzueRmVMSize should show more attributes than only support for accelerated networking. See also my request at https://feedback.azure.com/forums/34192--general-feedback/suggestions/35068363-get-azurermvmsize-should-show-additional-capabilit
(which bt the way has also not received any feedback from MS).
-
234 votes
Thank you for voting on this suggestion. It is now completed and can be done via custom Azure Policy. Here is a sample custom policy to apply a specific tag at the RG and have them inherited by the Resources in that RG: https://github.com/Azure/azure-policy/tree/master/samples/ResourceGroup/copy-resourcegroup-tag
Tag inheritance for existing resources is something that we plan to add support for in 2019.
Stanley Merkx
commented
Or you could create a policy that automatically pulls tags/values as defined at the resource group level if they are not provided during resource creation. See the 2nd example here: https://docs.microsoft.com/en-us/azure/governance/policy/concepts/definition-structure#policy-function-examples.
-
7 votesStanley Merkx
shared this idea
·
-
144 votesunder review ·
AdminAzure IaaS Engineering Team
(Azure IaaS Engineering Team, Microsoft, Microsoft Azure)
responded
This is something that we are reviewing to determine when we can support the functionality.
-
3 votesStanley Merkx
commented
And while we're at it: why does a marketplace image need a "plan" property which seemingly contains the same info as already present in the "imagereference" section?
This too makes it very difficult to have a single template that works for standard images and for marketplace images.
And there should be to accept an EULA from within a template: that would prevent "Error: Code=MarketplacePurchaseEligibilityFailed". Obviously this should be done in such a way that it doesn't interfere with regular non-marketplace images.
Stanley Merkx
shared this idea
·
-
31 votesStanley Merkx
supported this idea
·
-
8 votes
-
87 votes
Thank you for taking the time to vote on this request. Work on this has commenced. We will email you once it is completed.
If you are interested in participating in the preview please email back.
-
1,243 votes
We’re continuing to investigate options for adding this support. There are technical challenges to overcome in order to make this happen. We thank you for all your valuable comments so far, and welcome any additional feedback you have on what are the most important use cases involved with these scenarios.
Stanley Merkx
supported this idea
·
-
147 votesStanley Merkx
supported this idea
·
Stanley Merkx
commented
We really need this functionality as well, need to slice cost by department / application / project / etc. Resources can easily be tagged, but these tags cannot be used easily from the Power BI content pack.
-
10 votesStanley Merkx
supported this idea
·
Hmm, so setting the policy type to "indexed" fixed the policy: it now only applies to taggable resources so it's no longer non-compliant. IMHO that is just a workaround as these resources may still show up in billing/usage reports and should be recognisable by individual tags...