none
FAQ: How to group resources in Cloudyn by Azure Resource group tags

    Question

  • Hi

    I would like to create a custom dashboard, for all our customers (we are an CSP) that shows them their resource cost, grouped by the actual Resource groups they have in Azure. This is extremely relevant for all our customers, and are usually how they logically group their cost in one subscription by.

    Monday, October 2, 2017 12:56 PM

Answers

  • Overview: Azure Resource Group tags propagate into Cloudyn, but can only be used to filter certain report types. Other reports can be filtered based on Account tags created in Cloudyn instead. Cost Allocation Models can be configured to make sure that all of your resources are tagged in Cloudyn.

    Please Note: Azure EA customers can confirm that their data is correctly tags in the Azure billing file. If resources are uncategorized in Azure, they will show in the "Other" category in Cloudyn.

    Please also note: Tag names are case preservative in Azure, and case sensitive in Cloudyn. So, you will need to use the same case for tags in Azure to be able to group by those tags in Cloudyn. As a work around, you could also create a cost allocation model in Cloudyn that includes both cases/spellings of your resource tags as shown in Azure. Or use Category Manager to filter by both cases.

    For more information see the article on how to: Use custom tags to allocate costs in Cloudyn


    Please note: You need to add "ResourceGroup" and/or "ResourceGroupName" to your Cost Model in "Cost - Cost Management - Cost Allocation 360" before you can add a filter based on "ResourceGroup" and/or "ResourceGroupName" in "Cost - Cost Allocation Analysis - Cost Analysis".


    June 2018 Update: In Cloudyn, a tag called “ResourceGroup” is now generated with the name of the Azure resource group as its value. This “ResourceGroup” tag is now available for use in "Cost Allocation" after you add it to a cost model. (If you have any difficulty filtering by other tags, please try filtering by “ResourceGroup” and/or "ResourceGroupName"instead.)

     

    ACM limits the number of tags which are synced from Azure to prevent performance issues:

    • Azure Resource Group Tags = 20
    • Azure Resource Tags = 150

    (Resource tags will be grayed out if you are over the limit. You can request Cloudyn support to increase the limits with a valid business justification, but it can lead to performance issues).

    Supported: Azure Resource Tags are currently only available as filters on some Cloudyn reports.

    Azure Resource Tags are available as filters on the following Cloudyn Reports:

    • Assets - Resources - Azure Resource Explorer
    • Cost - Cost Analysis - Cost Navigator (Beta) 
      

    Unsupported: It is a common feature request to add the ability to filter by Azure Resource Tags in the following Cloudyn Reports:

    (To add, vote up, or check the status of a feature request please go to the ACM Feedback page.)

    • Cost - Cost Analysis - Actual Cost Over Time
    • Cost - Projection and Budget - Annual Projected Cost 
      (The tags available in these reports are "Account Tags" created in the Cloudyn accounts page instead of "Azure Resource Tags")
     


    Please also note:

    • Any changes you make to your Azure Resource Tags can take up to 24-72 hours to propagate to Cloudyn (per the standard Cloudyn Data Refresh Timelines).
    • For Azure EA customers, billing data is available to Cloudyn via the EA API key, but to see your tags in Cost reports your accounts need to be active so that you can see the usage data for your tags (Per the FAQ: How to add ARM credentials to fix "un-activated" accounts to view Azure usage data) Since CSP customers can't use ARM credentials at this time, they won't be able to sort based on Resource Tags in Cloudyn.
    • Azure doesn't currently support tagging “ASM/Classic” resources for billing purposes (but you can tag ARM virtual machines).
    • Azure doesn't currently support tag inheritance at the resource group level (so tags applied at the resource group level won't replicated top-down).

    You can also generate usage report from Azure to see how your data is tagged in Azure.




    Tuesday, March 6, 2018 10:32 PM

All replies

Tuesday, January 16, 2018 10:46 PM
  • Overview: Azure Resource Group tags propagate into Cloudyn, but can only be used to filter certain report types. Other reports can be filtered based on Account tags created in Cloudyn instead. Cost Allocation Models can be configured to make sure that all of your resources are tagged in Cloudyn.

    Please Note: Azure EA customers can confirm that their data is correctly tags in the Azure billing file. If resources are uncategorized in Azure, they will show in the "Other" category in Cloudyn.

    Please also note: Tag names are case preservative in Azure, and case sensitive in Cloudyn. So, you will need to use the same case for tags in Azure to be able to group by those tags in Cloudyn. As a work around, you could also create a cost allocation model in Cloudyn that includes both cases/spellings of your resource tags as shown in Azure. Or use Category Manager to filter by both cases.

    For more information see the article on how to: Use custom tags to allocate costs in Cloudyn


    Please note: You need to add "ResourceGroup" and/or "ResourceGroupName" to your Cost Model in "Cost - Cost Management - Cost Allocation 360" before you can add a filter based on "ResourceGroup" and/or "ResourceGroupName" in "Cost - Cost Allocation Analysis - Cost Analysis".


    June 2018 Update: In Cloudyn, a tag called “ResourceGroup” is now generated with the name of the Azure resource group as its value. This “ResourceGroup” tag is now available for use in "Cost Allocation" after you add it to a cost model. (If you have any difficulty filtering by other tags, please try filtering by “ResourceGroup” and/or "ResourceGroupName"instead.)

     

    ACM limits the number of tags which are synced from Azure to prevent performance issues:

    • Azure Resource Group Tags = 20
    • Azure Resource Tags = 150

    (Resource tags will be grayed out if you are over the limit. You can request Cloudyn support to increase the limits with a valid business justification, but it can lead to performance issues).

    Supported: Azure Resource Tags are currently only available as filters on some Cloudyn reports.

    Azure Resource Tags are available as filters on the following Cloudyn Reports:

    • Assets - Resources - Azure Resource Explorer
    • Cost - Cost Analysis - Cost Navigator (Beta) 
      

    Unsupported: It is a common feature request to add the ability to filter by Azure Resource Tags in the following Cloudyn Reports:

    (To add, vote up, or check the status of a feature request please go to the ACM Feedback page.)

    • Cost - Cost Analysis - Actual Cost Over Time
    • Cost - Projection and Budget - Annual Projected Cost 
      (The tags available in these reports are "Account Tags" created in the Cloudyn accounts page instead of "Azure Resource Tags")
     


    Please also note:

    • Any changes you make to your Azure Resource Tags can take up to 24-72 hours to propagate to Cloudyn (per the standard Cloudyn Data Refresh Timelines).
    • For Azure EA customers, billing data is available to Cloudyn via the EA API key, but to see your tags in Cost reports your accounts need to be active so that you can see the usage data for your tags (Per the FAQ: How to add ARM credentials to fix "un-activated" accounts to view Azure usage data) Since CSP customers can't use ARM credentials at this time, they won't be able to sort based on Resource Tags in Cloudyn.
    • Azure doesn't currently support tagging “ASM/Classic” resources for billing purposes (but you can tag ARM virtual machines).
    • Azure doesn't currently support tag inheritance at the resource group level (so tags applied at the resource group level won't replicated top-down).

    You can also generate usage report from Azure to see how your data is tagged in Azure.




    Tuesday, March 6, 2018 10:32 PM
  • Hi,

    I have a Pay-as-you-go accout and have setup tags in Azure on two resource groups. They have successfully replicated to Cloudyn. 

    However, when I go to COST ALLOCATION 360° there is no "Add" button. Any ideas why?

    Peter Björkmarker

    Monday, March 19, 2018 6:20 AM
  • How to view resources that are not tagged by a specific tag Azure Resource explorer in Cloudyn:

    In left hand menu in Azure Resource Explorer there is an option to choose the tag you want to monitor for untagged resources (this example uses the “test category” as the tag).
    After choosing tags, mark the check box: “exclude tag filters” below it.
    Then, go to show/hide tags on the top and choose the same tags as on the left, to add them as columns to the table.
    This will give you list of resources that don’t carry a value for these tag keys.
    Then, you can use the "show/hide fields" option to add the Resource ID and export the report.

     
    Thursday, October 25, 2018 8:01 PM
  • If you are expecting to see more unallocated data in Cloudyn...

    Please note: If a service in a cost allocation model has at least one tag in Azure, it’s considered “tagged” and the rule for untagged resources is not applied. Since the "ResourceGroupName" tag should exist for every service, if you include this tag in your cost allocation model, all your VMs and Storage will be considered tagged by the cost allocation model.

    There are few possible work arounds to see your data as unallocated:

    1. Use only one tag per cost allocation model.
    2. Create a separate model for the "ResourceGroupName" tag and do not include this tag to your other policies.
    3. Create a custom tag via Category Manager.
    Friday, December 14, 2018 12:49 AM