Update reports for improved meter names
Published date: June 27, 2018
Translate between the old and new meter names based on the meter ID (resource GUID)
You can use the following steps to filter the mapping spreadsheet we’ve provided to only the meters that you consume. Note that the examples are from a direct customer subscription. The values in each column might be different depending on your subscription.
- Download the list of standardized meters (you can find localized download files at the bottom of this page), and save the file locally (for example, c:\AzureMeterMapping-en.xlsx).
- Either download a detailed usage summary or create a workbook based on the output from one of the Azure APIs, and save the file locally (for example, c:\AzureUsage.xlsx). See an example using a detailed usage file below.
- If you're a CSP partner, download a usage-based reconciliation file from Partner Center. Note that currently, the unit of measure is not found in the reconciliation file.
- If you're a Direct customer, download the Version 2—Preview file from the Azure Account Portal.
- If you're an EA customer, download the Usage Detail report under Reports > Download Usage in the Enterprise Portal.
- Open the AzureUsage.xlsx file and remove any data that's unrelated to your daily usage (for example, statement or provisioning status information). Rename the worksheet to Sheet 1 if it isn’t already named Sheet 1.
- Clean up the data in AzureUsage.xlsx before running a vlookup to interpret meter naming changes.
- To ensure that vlookups return valid results, remove the quotation marks around the meter ID (resource GUID) of AzureUsage.xlsx by using the Find/Replace function in Excel. Then, move the Meter ID (Resource GUID) column to the left to become column A to help with vlookups, and save the file. Note that the variations in meter attribute names shown as column headers in the following table will depend on your specific Azure subscription.
A | B | C | D | E | F | G | H | |
1 | Meter ID (Resource GUID) | Usage Date | Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region) | Unit (Unit of Measure) | Consumed Quantity |
2 | a149966f-73b4-4e1d-b335-d2a572b1e6bd | 10/18/2017 | Data Services | SQL Database | Standard S0 Database Days | Days | ####.## | |
3 | a43a47f9-3dc0-4611-880e-52c71b55b612 | 10/18/2017 | Storage | Geo Redundant | Standard IO - Block Blob (GB) | DE Northeast | GB | ####.## |
4 | 2005544f-659d-49c9-9094-8e0aea1be3a5 | 10/18/2017 | Virtual Machines | A1 VM (Windows) | Compute Hours | US Central | Hours | ####.## |
5. Open the AzureMeterMapping-en.xlsx file and build a standard vlookup on the meter ID (resource GUID) to the AzureUsage.xlsx file.
- Add a column to the right of column A in the AzureMeterMapping-en.xlsx file.
- Enter the vlookup function in cell B2: =VLOOKUP(A2,'[AzureUsage.xlsx]Sheet 1'!$A:$A,1,FALSE)
- Filter out the "N/A" values from column B to eliminate any meters you don't use. Your updated file will look like the following example.
A | B | C | D | E | F | G | H | I | J | K | L | |
1 | Meter ID or Resource GUID | Old convention - Service Name, Name, or Meter Category | Old convention - Service Type, Type, or Meter Sub-category | Old convention - Resource Name, Resource, Service Resource or Meter Name | Old convention - Meter Region or Region | Old convention - Unit or Unit of Measure | New convention - Service Name, Name, or Meter Category | New convention - Service Type, Type, or Meter Sub-category | New convention - Resource Name, Resource, Service Resource or Meter Name | New convention - Meter Region or Region | New convention - Unit or Unit of Measure | |
2 | a149966f-73b4-4e1d-b335-d2a572b1e6bd | a149966f-73b4-4e1d-b335-d2a572b1e6bd | Data Services | SQL Database | Standard S0 Database Days | Days | SQL Database | Single Standard | S0 DTUs | 1/Day | ||
3 | 2005544f-659d-49c9-9094-8e0aea1be3a5 | 2005544f-659d-49c9-9094-8e0aea1be3a5 | Storage | Geo Redundant | Standard IO - Block Blob (GB) | DE Northeast | GB | Storage | General Block Blob | GRS Data Stored | DE Northeast | 1 GB/Month |
4 | a43a47f9-3dc0-4611-880e-52c71b55b612 | a43a47f9-3dc0-4611-880e-52c71b55b612 | Virtual Machines | A1 VM (Windows) | Compute Hours | US Central | Hours | Virtual Machines | A Series Windows | A1 | US Central | 1 Hour |
- The results in the AzureMeterMapping-en.xlsx file will display only the meters you have consumed that are in your usage summary. See columns C through G for the old meter naming conventions. See columns H through L for the new naming conventions.
Summarize my usage and see both old and new names displayed in one report by using a pivot table before the name changes take effect
This section provides guidance on how to summarize the meters you’ve consumed into one combined report that displays both the old and new names. Follow these instructions if you want to see how your reports will look after the new names are implemented. You can learn more about the improvements to meter names. Note that the examples below are from a Direct customer subscription. The values in each column might be different depending on your subscription.
- Download the list of standardized names (you can find localized download files at the bottom of this page), and save the file locally (for example, c:\AzureMeterMapping-en.xlsx).
- Either download a detailed usage summary or create a workbook based on the output from one of the Azure APIs, and save the file locally (for example, c:\AzureUsage.xlsx). See an example using a detailed usage file below.
- If you're a CSP partner, download a usage-based reconciliation file from Partner Center. Note that currently, the unit of measure is not found in the reconciliation file.
- If you're a Direct customer, download the Version 2—Preview file from the Azure Account Portal.
- If you're an EA customer, download the Usage Detail report under Reports > Download Usagein the Enterprise Portal.
- Open the AzureUsage.xlsx file and remove any data that's unrelated to your daily usage (for example, statement or provisioning status information).
- Clean up the data in AzureUsage.xlsx before running a vlookup to interpret meter naming changes.
- To ensure that vlookups return valid results, remove the quotation marks around all cells of the AzureUsage.xlsx file by using the Find/Replace function in Azure. Then, move the Meter ID (Resource GUID) column to the left to become column A to help with vlookups, and save the file. Note that the variations in meter attribute names shown as column headers in the table below will depend on your specific Azure subscription.
- Open a new Excel file and name it Usage Summary – New Names.xlsx. Save the file locally.
- Copy and paste the data from the AzureUsage.xlsx file to the Usage Summary – New Names.xlsx file in the order shown in the following example.
A | B | C | D | E | F | G | H | |
1 | Meter ID (Resource GUID) | Usage Date | Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region) | Unit (Unit of Measure) | Consumed Quantity |
2 | a149966f-73b4-4e1d-b335-d2a572b1e6bd | 10/18/2017 | Data Services | SQL Database | Standard S0 Database Days | Days | ####.## | |
3 | a43a47f9-3dc0-4611-880e-52c71b55b612 | 10/18/2017 | Storage | Geo Redundant | Standard IO - Block Blob (GB) | DE Northeast | GB | ####.## |
4 | 2005544f-659d-49c9-9094-8e0aea1be3a5 | 10/18/2017 | Virtual Machines | A1 VM (Windows) | Compute Hours | US Central | Hours | ####.## |
7. In the Usage Summary – New Names.xlsx file, build a vlookup in columns O–S to pull in columns G–K in the AzureMeterMapping-en.xlsx file. Include the headers as well. See the following example.
A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | ||
1 | Meter ID or Resource GUID | Usage Date | Service Name, Name, or Meter Category | Service Type, Type, or Meter Sub-category | Resource Name, Resource, Service Resource or Meter Name | Meter Region or Region | Unit or Unit of Measure | Consumed Quantity | Sub Region | Service | Component | Service Info 1 | Service Info 2 | Additional Info | New convention - Service Name, Name, or Meter Category | New convention - Service Type, Type, or Meter Sub-category | New convention - Resource Name, Resource, Service Resource or Meter Name | New convention - Meter Region or Region | New convention - Unit or Unit of Measure | |
2 | a149966f-73b4-4e1d-b335-d2a572b1e6bd | 10/18/2017 | Data Services | SQL Database | Standard S0 Database Days | Days | ####.## | “Data Services” | “XXXXXXXX” | SQL Database | Single Standard | S0 DTUs | 1/Day | |||||||
3 | a43a47f9-3dc0-4611-880e-52c71b55b612 | 10/18/2017 | Storage | Geo Redundant | Standard IO - Block Blob (GB) | DE Northeast | GB | ####.## | “xxx” | “Storage” | “XXXXXXXX” | Storage | General Block Blob | GRS Data Stored | DE Northeast | 1 GB/Month | ||||
4 | 2005544f-659d-49c9-9094-8e0aea1be3a5 | 10/18/2017 | Virtual Machines | A1 VM (Windows) | Compute Hours | US Central | Hours | ####.## | “xxx” | “Virtual Machines” | “XXXXXXXX” | Virtual Machines | A Series Windows | A1 | US Central | 1 Hour | ||||
8. Build a pivot from the Usage Summary – New Names.xlsx file.
- Add a new sheet to the Usage Summary – New Names.xlsx file workbook and name the sheet After-Before Summary.
- Highlight all cells in the Usage Summary – New Names.xlsx file.
- Select the Insert tab and select PivotTable. Create the Pivot table to After-Before Summary sheet.
- Add the following PivotTable fields to Rows:
- Meter ID (Resource GUID)
- Meter Category (Service Name or Name)
- Meter Sub-category (Service Type or Type)
- Meter Name (Resource Name, Resource, Service Resource)
- Meter Region (Region)
- Unit (Unit of Measure)
- New convention - Service Name, Name, or Meter Category
- New convention - Service Type, Type, or Meter Sub-category
- New convention - Resource Name, Resource, Service Resource or Meter Name
- New convention - Meter Region or Region
- New convention - Unit or Unit of Measure
- Add the Consumed Quantity field to Values as a Sum of Consumed Quantity.
- Go to the Design tab and select Report Layout. Select Show in Tabular Form in the drop-down menu.
- Right-click each column header and clear “Subtotal<header name>” (for example, Subtotal “Meter Category (Service Name or Name)”).
Your final output should look like the following example:
A | B | C | D | E | F | G | H | I | J | K | L | |
1 | Meter ID (Resource GUID) | Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region)
| Unit (Unit of Measure) | New convention - Service Name, Name, or Meter Category | New convention - Service Type, Type, or Meter Sub-category | New convention - Resource Name, Resource, Service Resource or Meter Name | New convention - Meter Region or Region | New convention - Unit or Unit of Measure | Sum of Consumed |
2 | a149966f-73b4-4e1d-b335-d2a572b1e6bd | Data Services | SQL Database | Standard S0 Database Days | Days | SQL Database | Single Standard | S0 DTUs | 1/Day | #### | ||
3 | 2005544f-659d-49c9-9094-8e0aea1be3a5 | Storage | Geo Redundant | Standard IO - Block Blob (GB) | DE Northeast | GB | Storage | General Block Blob | GRS Data Stored | DE Northeast | 1 GB/Month | #### |
4 | 30ab1dae-8172-4b24-aa5b-3666d3f0fde1 | Virtual Machines | A1 VM (Windows) | Compute Hours | US Central | Hours | Virtual Machines | A Series Windows | A1 | US Central | 1 Hour | #### |
10 | #### |
Summarize my usage and see both old and new names displayed in one report by using a pivot table after the name changes take effect
This section provides guidance on how to summarize the meters you’ve consumed into one combined report that displays both the old and new names. Follow these instructions if you need to keep using the old names in your reports temporarily after the new names are implemented. You can learn more about the improvements to meter names. Note that the following examples are from a Direct customer subscription. The values in each column might be different depending on your subscription.
- Download the list of standardized meters (you can find localized download files at the bottom of this page), and save the file locally (for example, c:\AzureMeterMapping-en.xlsx).
- Either download a detailed usage summary or create a workbook based on the output from one of the Azure APIs, and save the file locally (for example, c:\AzureUsage.xlsx). See an example using a detailed usage file below.
- If you're a CSP partner, download a usage-based reconciliation file from Partner Center. Note that currently, the unit of measure is not found in the reconciliation file.
- If you're a Direct customer, download the Version 2—Preview file from the Azure Account Portal.
- If you are an EA customer, download the Usage Detail report under Reports > Download Usage in the Enterprise Portal.
- Open a new Excel file and name it Usage Summary – Old Names.xlsx. Save the file locally.
- Clean up the data in AzureUsage.xlsx before running a vlookup to interpret meter naming changes.
- To ensure that vlookups return valid results, remove the quotation marks around all cells of the AzureUsage.xlsx file by using the Find/Replace function in Excel. Then, move the Meter ID (Resource GUID) column to the left to become column A to help with vlookups, and save the file. Note that the variations in meter attribute names shown as column headers in the following table will depend on your specific Azure subscription.
- Copy and paste the data from the AzureUsage.xlsx file to the Usage Summary – Old Names.xlsx file in the order shown in the following example.
A | B | C | D | E | F | G | H | |
1 | Meter ID (Resource GUID) | Usage Date | Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region) | Unit (Unit of Measure) | Consumed Quantity |
2 | “a149966f-73b4-4e1d-b335-d2a572b1e6bd” | 10/18/2017 | “SQL Database” | “Single Standard” | “S0 DTUs” | “1/Day” | ####.## | |
3 | “a43a47f9-3dc0-4611-880e-52c71b55b612” | 10/18/2017 | “Storage” | “General Block Blob” | “GRS Data Stored” | “DE Northeast” | “1 GB/Month” | ####.## |
4 | “2005544f-659d-49c9-9094-8e0aea1be3a5” | 10/18/2017 | “Virtual Machines” | “A Series Windows” | “A1” | “US Central” | “1 Hour” | ####.## |
6. In the Usage Summary – Old Names.xlsx file, build a vlookup in columns O–S to pull in columns B–F in the AzureMeterMapping-en.xlsx file. Include the headers as well. See the following example.
A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | ||
1 | Meter ID (Resource GUID) | Usage Date | Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region) | Unit (Unit of Measure) | Consumed Quantity | Sub Region | Service | Component | Service Info 1 | Service Info 2 | Additional Info | Old convention - Service Name, Name, or Meter Category | Old convention - Service Type, Type, or Meter Sub-category | Old convention - Resource Name, Resource, Service Resource or Meter Name | Old convention - Meter Region or Region | Old convention - Unit or Unit of Measure | |
2 | a149966f-73b4-4e1d-b335-d2a572b1e6bd | 10/18/2017 | SQL Database | Single Standard | S0 DTUs | 1/Day | ####.## | "Data Services" | “XXXXXXXX” | Data Services | SQL Database | Standard S0 Database Days | Days | |||||||
3 | a43a47f9-3dc0-4611-880e-52c71b55b612 | 10/18/2017 | Storage | General Block Blob | GRS Data Stored | DE Northeast | 1 GB/Month | ####.## | “xxx” | "Virtual Machines" | “XXXXXXXX” | Storage | Geo Redundant | Standard IO - Block Blob (GB) | DE Northeast | GB | ||||
4 | 2005544f-659d-49c9-9094-8e0aea1be3a5 | 10/18/2017 | Virtual Machines | A Series Windows | A1 | US Central | 1 Hour | ####.## | “xxx” | “Storage” | “XXXXXXXX” | Virtual Machines | A1 VM (Windows) | Compute Hours | US Central | Hours | ||||
7. Build a pivot from the Usage Summary – Old Names.xlsx file.
- Add a new sheet to the Usage Summary – New Names.xlsx file workbook, and name the sheet After-Before Summary.
- Highlight all cells in the Usage Summary – New Names.xlsx file.
- Select the Insert tab and select PivotTable. Create the Pivot table to After-Before Summary sheet.
- Add the following PivotTable fields to Rows:
- Meter ID (Resource GUID)
- Meter Category (Service Name or Name)
- Meter Sub-category (Service Type or Type)
- Meter Name (Resource Name, Resource, Service Resource)
- Meter Region (Region)
- Unit (Unit of Measure)
- Old convention - Service Name, Name, or Meter Category
- Old convention - Service Type, Type, or Meter Sub-category
- Old convention - Resource Name, Resource, Service Resource or Meter Name
- Old convention - Meter Region or Region
- Old convention - Unit or Unit of Measure
- Add the Consumed Quantity field to Values as a Sum of Consumed Quantity.
8. Go to the Design tab and select Report Layout. Select Show in Tabular Form in the drop-down menu.
- Right-click each column header and clear Subtotal“<header name>” (for example, Subtotal “Meter Category (Service Name or Name)”).
Your final output should look like the following example:
A | B | C | D | E | F | G | H | I | J | K | L | |
1 | Meter ID (Resource GUID) | Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region)
| Unit (Unit of Measure) | Old convention - Service Name, Name, or Meter Category | Old convention - Service Type, Type, or Meter Sub-category | Old convention - Resource Name, Resource, Service Resource or Meter Name | Old convention - Meter Region or Region | Old convention - Unit or Unit of Measure | Sum of Consumed |
2 | a149966f-73b4-4e1d-b335-d2a572b1e6bd | SQL Database | Single Standard | S0 DTUs | 1/Day | Data Services | SQL Database | Standard S0 Database Days | Days | ### | ||
3 | a43a47f9-3dc0-4611-880e-52c71b55b612 | Storage | General Block Blob | GRS Data Stored | DE Northeast | 1 GB/Month | Storage | Geo Redundant | Standard IO - Block Blob (GB) | DE Northeast | GB | ### |
4 | 2005544f-659d-49c9-9094-8e0aea1be3a5 | Virtual Machines | A Series Windows | A1 | US Central | 1 Hour | Virtual Machines | A1 VM (Windows) | Compute Hours | US Central | Hours | ### |
10 | ### |
Translate the old to new names without the meter ID (resource GUID)
You can use the following steps to filter the mapping spreadsheet we’ve provided to only the meters that you consume based solely on the meter name attributes. You would use these steps before the name changes take effect if you don't have a usage file with the meter ID (resource GUID). You can learn more about the improvements to meter names.
- Download the list of standardized names (you can find localized download files at the bottom of this page), and save the file locally (for example, c:\AzureMeterMapping-en.xlsx).
- Open a new Excel file and name the file (for example, Old Names.xlsx). Save the file locally. Add the headers shown in the following example, and customize them based on your Azure subscription.
A | B | C | D | E | |
1 | Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region)
| Unit (Unit of Measure) |
2 |
3. Add the old name data from your file to the Old Names.xlsx file based on the headers you’ve created. See the following example.
A | B | C | D | E | |
1 | Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region)
| Unit (Unit of Measure) |
2 | Data Services | SQL Database | Standard S0 Database Days | Days | |
3 | Storage | Geo Redundant | Standard IO - Block Blob (GB) | DE Northeast | GB |
4 | Virtual Machines | A1 VM (Windows) | Compute Hours | US Central | Hours |
4. In the Old Names.xlsx file, in column F, you need to concatenate the data in each row. Enter the following formula in cell F2: =CONCATENATE(A2," ",B2," ",C2," ",D2," ",E2). See the following example.
A | B | C | D | E | F | |
1 | Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region)
| Unit (Unit of Measure) | |
2 | Data Services | SQL Database | Standard S0 Database Days | Days | Data Services SQL Database Standard S0 Database Days Days | |
3 | Storage | Geo Redundant | Standard IO - Block Blob (GB) | DE Northeast | GB | Storage Geo Redundant Standard IO – Block Blob (GB) DE Northeast GB |
4 | Virtual Machines | A1 VM (Windows) | Compute Hours | US Central | Hours | Virtual Machines A1 VM (Windows) Compute Hours US Central Hours |
- Copy and paste the content in column F as text only. This will remove formulas but keep the results in the cells. Then, move column F to column A. Your file should appear like the following one.
A | B | C | D | E | F | |
1 |
| Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region)
| Unit (Unit of Measure) |
2 | Data Services SQL Database Standard S0 Database Days Days | Data Services | SQL Database | Standard S0 Database Days | Days | |
3 | Storage Geo Redundant Standard IO – Block Blob (GB) DE Northeast GB | Storage | Geo Redundant | Standard IO - Block Blob (GB) | DE Northeast | GB |
4 | Virtual Machines A1 VM (Windows) Compute Hours US Central Hours | Virtual Machines | A1 VM (Windows) | Compute Hours | US Central | Hours |
5. In the AzureMeterMapping-en.xlsx file, add a column after column F. In column G, repeat step 4 by concatenating columns B–F.
6. In the AzureMeterMapping-en.xlsx file, add another column to the right side of column G.
7. Build a standard vlookup on column G in the AzureMeterMapping-en.xlsx file to column A in the Old Names.xlsx file. The legacy names might have changed over time and therefore won't display a match. See your current detailed usage summary from the Azure Management Portal to find the current name of your meter if a match is not found.
8. Filter column H to remove results with "N/A." After you’ve filtered, the AzureMeterMapping-en.xlsx file will only display the meters in your Old Names.xlsx file. To view the new names aligned for the meters in your Old Names.xlsx file, scroll to the right of the workbook to view columns I–M. See the results in the following example.
A | B | C | D | E | F | G | H | I | J | K | L | M | |
1 | Meter ID or Resource GUID | Old convention - Service Name, Name, or Meter Category | Old convention - Service Type, Type, or Meter Sub-category | Old convention - Resource Name, Resource, Service Resource or Meter Name | Old convention - Meter Region or Region | Old convention - Unit or Unit of Measure | New convention - Service Name, Name, or Meter Category | New convention - Service Type, Type, or Meter Sub-category | New convention - Resource Name, Resource, Service Resource or Meter Name | New convention - Meter Region or Region | New convention - Unit or Unit of Measure | ||
2 | a149966f-73b4-4e1d-b335-d2a572b1e6bd | Data Services | SQL Database | Standard S0 Database Days | Days | Data Services SQL Database Standard S0 Database Days Days | Data Services SQL Database Standard S0 Database Days Days | SQL Database | Single Standard | S0 DTUs | 1/Day | ||
3 | a43a47f9-3dc0-4611-880e-52c71b55b612 | Storage | Geo Redundant | Standard IO - Block Blob (GB) | DE Northeast | GB | Storage Geo Redundant Standard IO – Block Blob (GB) DE Northeast GB | Storage Geo Redundant Standard IO – Block Blob (GB) DE Northeast GB | Storage | General Block Blob | GRS Data Stored | DE Northeast | 1 GB/Month |
4 | 2005544f-659d-49c9-9094-8e0aea1be3a5 | Virtual Machines | A1 VM (Windows) | Compute Hours | US Central | Hours | Virtual Machines A1 VM (Windows) Compute Hours US Central Hours | Virtual Machines A1 VM (Windows) Compute Hours US Central Hours | Virtual Machines | A Series Windows | A1 | US Central | 1 Hour |
Translate the new to old names without the meter ID (resource GUID)
You can use the following steps to filter the mapping spreadsheet we’ve provided to only the meters that you consume based solely on the meter name attributes. You would use these steps after the name changes take effect if you don't have a usage file with the meter ID (resource GUID). You can learn more about the improvements to meter names.
- Download the list of standardized meters (you can find localized download files at the bottom of this page), and save the file locally (for example, c:\AzureMeterMapping-en.xlsx).
- Open a new Excel file and name the file (for example, New Names.xlsx). Save the file locally. Add the headers shown in the following example, and customize them based on your Azure subscription.
A | B | C | D | E | |
1 | Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region)
| Unit (Unit of Measure) |
2 |
3. Add the new name data from your file to the New Names.xlsx file based on the headers you’ve created. See the following example.
A | B | C | D | E | |
1 | Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region)
| Unit (Unit of Measure) |
2 | SQL Database | Single Standard | S0 DTUs | 1/Day | |
3 | Storage | General Block Blob | GRS Data Stored | DE Northeast | 1 GB/Month |
4 | Virtual Machines | A Series Windows | A1 | US Central | 1 Hour |
4. In the New Names.xlsx file, in column F, you need to concatenate the data in each row. Enter the following formula in cell F2: =CONCATENATE(A2," ",B2," ",C2," ",D2," ",E2). See the following example.
A | B | C | D | E | F | |
1 | Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region)
| Unit (Unit of Measure) | |
2 | SQL Database | Single Standard | S0 DTUs | 1/Day | SQL Database Single Standard s0 DTUs 1/Day | |
3 | Storage | General Block Blob | GRS Data Stored | DE Northeast | 1 GB/Month | Storage General Block Blob GRS Data Stored DE Northeast 1 GB/Month |
4 | Virtual Machines | A Series Windows | A1 | US Central | 1 Hour | Virtual Machines A Series Windows A1 US Central 1 Hour |
- Copy and paste the content in column F as text only. This will remove formulas but keep the results in the cells. Then, move column F to column A.
A | B | C | D | E | F | |
1 |
| Meter Category (Service Name or Name) | Meter Sub-category (Service Type or Type) | Meter Name (Resource Name, Resource, Service Resource) | Meter Region (Region)
| Unit (Unit of Measure) |
2 | SQL Database Single Standard s0 DTUs 1/Day | SQL Database | Single Standard | S0 DTUs | 1/Day | |
3 | Storage General Block Blob GRS Data Stored DE Northeast 1 GB/Month | Storage | General Block Blob | GRS Data Stored | DE Northeast | 1 GB/Month |
4 | Virtual Machines A Series Windows A1 US Central 1 Hour | Virtual Machines | A Series Windows | A1 | US Central | 1 Hour |
5. In the AzureMeterMapping-en.xlsx file, in column L, repeat step 4 by concatenating columns G–K.
6. Build a standard vlookup on column G in the AzureMeterMapping-en.xlsx file to column A in the Old Names.xlsx file. The legacy names might have changed over time and therefore won't display a match. See your current detailed usage summary from the Azure Management Portal to find the current name of your meter if a match is not found.
7. Filter column M to remove results with "N/A." After you’ve filtered, the AzureMeterMapping-en.xlsx file will only display the meters in your New Names.xlsx file. To view the old names aligned for the meters in your New Names.xlsx file, scroll to the left of the workbook to view columns B–F. See the results in the following example.
A | B | C | D | E | F | G | H | I | J | K | L | M | |
1 | Meter ID or Resource GUID | Old convention - Service Name, Name, or Meter Category | Old convention - Service Type, Type, or Meter Sub-category | Old convention - Resource Name, Resource, Service Resource or Meter Name | Old convention - Meter Region or Region | Old convention - Unit or Unit of Measure | New convention - Service Name, Name, or Meter Category | New convention - Service Type, Type, or Meter Sub-category | New convention - Resource Name, Resource, Service Resource or Meter Name | New convention - Meter Region or Region | New convention - Unit or Unit of Measure | ||
2 | a149966f-73b4-4e1d-b335-d2a572b1e6bd | Data Services | SQL Database | Standard S0 Database Days | Days | SQL Database | Single Standard | S0 DTUs | 1/Day | SQL Database Single Standard s0 DTUs 1/Day | SQL Database Single Standard s0 DTUs 1/Day | ||
3 | a43a47f9-3dc0-4611-880e-52c71b55b612 | Storage | Geo Redundant | Standard IO - Block Blob (GB) | DE Northeast | GB | Storage | General Block Blob | GRS Data Stored | DE Northeast | 1 GB/Month | Storage General Block Blob GRS Data Stored DE Northeast 1 GB/Month | Storage General Block Blob GRS Data Stored DE Northeast 1 GB/Month |
4 | 2005544f-659d-49c9-9094-8e0aea1be3a5 | Virtual Machines | A1 VM (Windows) | Compute Hours | US Central | Hours | Virtual Machines | A Series Windows | A1 | US Central | 1 Hour | Virtual Machines A Series Windows A1 US Central 1 Hour | Virtual Machines A Series Windows A1 US Central 1 Hour |
Download language versions of the naming mapping file
This section provides translated meter mapping files for different locales. Select the language to download the translated meter mapping file for the indicated locale. You can learn more about the improvements to Azure names.
Language | Locale |
cs | |
da | |
de | |
el | |
en | |
es | |
fi | |
fr | |
hu | |
It | |
ja | |
Ko | |
nb | |
nl | |
pl | |
pt-br | |
pt-pt | |
ro | |
ru | |
sv | |
tr-tr | |
zh-hk | |
zh-cn | |
zh-sg |
Contact Support
If you have further questions concerning the naming changes, please contact Azure Support.