This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
As can be seen in the attachment, Azure provide two region name standards via the API; PricesExtract.Items.armRegionName which is currently used as the second part of the region name in cloudability, and PricesExtract.Items.location which currently differs from the first part of the Cloudability region name.
The issue this causes is that consumer produce reports from both Azure and Cloudability, the current mismatch of region names causes confusion when trying to map the data.
In the attachment we have provided a view of what we think the Cloudability region name should looks like (PricesExtract.Items.location::PricesExtract.Items.armRegionName)
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
The other reason this is really important is that currently when you sort alphabetically you get all the Easts together and all the Wests together, etc... whereas using the MS standard you'll get all the countries Retogether... EU North, EU West, IN Central, IN West, US Central, US East, etc...
Alphabetical sort order currently:
Cloudability Region Name
Central India::centralindia
Central US::centralus
East Asia::eastasia
East US 2::eastus2
East US::eastus
North Central US::northcentralus
North Europe::northeurope
South Central US::southcentralus
Southeast Asia::southeastasia
West Europe::westeurope
West India::westindia
West US 2::westus2
West US::westus
Recommended Cloudability Region Name
AP East::eastasia
AP Southeast::southeastasia
EU North::northeurope
EU West::westeurope
IN Central::centralindia
IN West::westindia
US Central::centralus
US East 2::eastus2
US East::eastus
US North Central::northcentralus
US South Central::southcentralus
US West 2::westus2
US West::westus
Completely agree. The current "pretty name" portion in Cloudability doesn't align with the official "pretty" region name (available in the location column in the Azure pricing API).