Over this weekend we released a new version of Cloud Portam. In the release we have included enhancements to storage account management functionality and some other changes. This blog post talks about the enhancements we have done in this release.

Summary of Enhancements

  • View storage account size
  • Change storage account type
  • Manage storage account tags
  • Manage storage account custom domains
  • Cloud service diagnostics enhancements

Rest of this post talks about these enhancements.

View Storage Account Size

One of the biggest asks I have seen around is the ability to view the total size of a storage account. While one can see the size of blob storage via storage analytics but there’s no direct way to see the size of table/queue storage. I’m pleased to announce that Cloud Portam enables you to view the size of table/queue storage and give you the total size of a storage account. We have accomplished this by consuming Azure Billing API in Cloud Portam. What we do is we fetch the billing API for last 7 days and extract information related to your storage accounts and show you the size of your storage accounts.

SNAGHTMLc6150f8

Not only that you can view the breakup by service type as well.

SNAGHTMLc62e17b

A few things I would like to mention here:

  • As mentioned above, the data is fetched from the billing API and there is a possibility that there is some delay in receipt of data by Azure billing system thus the sizes shown are estimates only. Always refer to Azure Billing Portal for most accurate information about storage size.
  • If the billing API doesn’t return data for a storage account, Cloud Portam does not display the data. That does not mean that storage account does not contain any data.

Change Storage Account Type

I’m pleased to announce that using Cloud Portam you can change the account type of a storage account. For example, you can change a GRS account to RA-GRS account.

SNAGHTMLc69231b

SNAGHTMLc6b0345

A few things I want to mention here:

  • Azure only allows you to change account types for the following storage account types – Standard LRS, Standard GRS, and Standard RA-GRS today. Thus you won’t be able to change account types of Standard ZRS and Premium LRS type storage accounts.
  • Changing account type is supported for both “Classic” and “Resource Manager” storage accounts.
  • Changing account type is backed by role-based access control. Thus you will be able to perform this operation if you have permission to do so.

Manage Storage Account Tags

I’m pleased to announce that using Cloud Portam you can manage tags for your Azure Storage accounts. You can create new tags for your storage accounts, remove or update existing tags from your storage accounts.

SNAGHTML1605ff06

SNAGHTML16072297

A few things I want to mention here:

  • Tags management is not supported for “Classic” storage account. Thus you will not even see the option of managing tags for those storage accounts.
  • Tags management is backed by role-based access control. Thus you will only be able to manage tags on a storage account if you have permission to do so.
  • Currently Azure Resource Manager API only allows you to have a maximum of 15 tags per storage account and Cloud Portam supports that. If you try to create more than 15 tags for a storage account, Cloud Portam will not let you do that.

Manage Custom Domains for Storage Accounts

You can map a custom domain to the blob storage endpoint of a storage account. For example, if your website address is “myawesomewebsite.com” but you want to serve images from your blob storage using a custom domain like “staticcontent.myawesomewebsite.com”, you can do so and Cloud Portam helps you in setting up custom domain for your blob storage endpoint.

The way it works is that you first go to your domain registrar (Godaddy.com for example) and create a CNAME mapping between your custom domain name (“staticcontent” in our example) and your storage account blob storage endpoint (“youraccountname.blob.core.windows.net”). Then you come to Cloud Portam and use “Custom Domain” management functionality to tell Azure about this mapping.

SNAGHTML160d2837

SNAGHTML161056ca

SNAGHTML16115fbf

Once you save this setting, then you will be able to access the contents of your blob storage using a custom domain instead of using default blob storage URL.

Please note that as of today you can’t have multiple custom domains pointing to same storage account. In order to change this setting you will need to remove the existing setting first. Cloud Portam also allows you to do that.

SNAGHTML1617e491

Once you remove the mapping, you can add another custom domain mapping.

A few things I want to mention here:

  • Custom domain management is not supported for “Classic” storage account. Thus you will not even see the option of managing custom domains for those storage accounts.
  • Custom domain management is backed by role-based access control. Thus you will only be able to manage custom domain on a storage account if you have permission to do so.

Cloud Service Diagnostics Enhancements

A few weeks ago we introduced historical data search for your Cloud Service diagnostics data. One of the things you could do there was filter historical data by your Cloud Service Role/Role Instance names. However the issue was that you have to manually type in this information. One of our users Koren suggested that there should be a way to select the role/role instances names (Thank You Koren for making this useful suggestion!). I’m pleased to announce that in this version we have introduced the functionality where in the application can parse configuration file of your Cloud Service (*.cscfg) to give you a list of role/role instance names.

image

Once you select the configuration file, the application parses that file and gets the name of the roles and their current instance count. Based on that it gives you a multi-select pulldown menu.

image

image

Then when you search for historical data, data is filtered for the selected role/role instance names.

A few things I want to mention here:

  • We do realize that the configuration file contains secret information (account keys, connection strings etc.) related to your application thus we don’t store the contents of the file anywhere in our application at any time. We simply parse this file to get the role name and the instances count for a role and discard that file.
  • It is completely optional for you to specify the configuration file. You can still manually type in the role/role instance names.

What’s Next

There are a number of things in our immediate product pipeline. We will continue enhancing our Subscription management features by adding support for managing additional services, surfacing billing data etc. So stay tuned for all these changes.

Try It Out!

We humbly request you to try out these updates in Cloud Portam. This is available in both “Personal” and “Team” editions of Cloud Portam. Though extreme care has been taken regarding testing the current functionality, it is quite possible that we may have overlooked something. If you find something missing or implemented incorrectly, please feel free to reach out to us and tell us. We will fix the issues ASAP.

Closing

As you can see we’re constantly investing in making the product more and more useful. Do try out Cloud Portam and these features and let us know what you think. If you think, we can improve it in any way, please feel free to share your thoughts. The link to our website is http://www.cloudportam.com.