Set up for Azure Rightsizing with our platform is a three-stage process. First, enable utilization metrics collection for all subscriptions, if you have not done so already. Second, permit Cloudability to access resource information needed to build the Rightsizing model. Third, permit Cloudability to access memory utilization metrics.

Stage 1: Enable utilization metrics collection

Stage 2: Enable access to resource information

Stage 3: Enable access to utilization metrics

---

 

Stage 3: Enable access to utilization metrics

This guide will help you setup access to Azure memory utilization metrics within Cloudability that we'll need to build the Rightsizing model.

Prerequisites

Before you begin the process, ensure that:

1. You are a Cloudability administrator
2. You are either Owner or Contributor of the Subscriptions you would like to credential
3. You have enabled diagnostic metrics for Azure Compute VMs in the Subscriptions you'll credential

 

Permissions you are granting Cloudability

To retrieve utilization metrics from the storage tables, Cloudability requires the shared access signature tokens with the checked permission in the screenshot below. Additional information is in the Azure Portal > Storage accounts > Select a subscription > Shared access signature.

 

Cloudability Setup

To obtain memory utilization data from Azure, we will need to access the storage tables where Azure writes utilization metrics. Grant Cloudability permission to the storage tables for your subscription(s) by completing the following steps. 

1. As a Cloudability administrator, navigate to the Vendor Credentials page.

2. Select the edit pencil icon along on the row for any Subscription.

3. Click on the Select Subscriptions under Storage Accounts.

4. Select the Subscription(s) for which you will generate Storage Account SAS tokens and select Ok.

5. Select Download Script.

6. Copy downloaded PowerShell script named cloudability-generate-sas-tokens-<DATETIME>.ps1 to your Windows environment.

7. Run PowerShell as administrator.

8. Ensure you have downloaded Azure SDKs for PowerShell.

9. Log in to PowerShell by running the command Login-AzureRmAccount.

10. Change the execution policy by running the command Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process.

11. Open a PowerShell window and run Enable-AzureRmAlias - this enables all AzureRm prefixes for the current PowerShell session.

12. Run the PowerShell script named cloudability-generate-sas-tokens-<DATETIME>.ps1.

13. Open the generated file named cloudability-SAStokens-<DATETIME>.json and check that the file contains content similar to the below.

[
    {
        "storage_account_id":  "/subscriptions/a3039555-9831-47ed-ab18-9a34cab87881/resourceGroups/Staging-US/providers/Microsoft.Storage/storageAccounts/stagingdiag667",
        "expiry":  "2018-04-29T20:44:01Z",
        "storage_account_resource_group":  "Staging-US",
        "subscription_guid":  "a3039555-9831-47ed-ab18-9a34cab87881",
        "token":  "?sv=2017-04-17\u0026sig=KrF5lkwJmpRD%2Bo4AxZPMc1egcmwYxYbOYiElgjj7iXw%3w\u0026se=2018-04-29T20%3A44%3A01Z\u0026srt=sco\u0026ss=t\u0026sp=rl",
        "resource_uri":  "https://stagingdiag667.table.core.windows.net/"
    },
    {
        "storage_account_id":  "/subscriptions/c2771d27-bbec-81d3-855b-299988aa34a4/resourceGroups/Prod-US/providers/Microsoft.Storage/storageAccounts/proddiag228",
        "expiry":  "2018-04-29T20:44:01Z",
        "storage_account_resource_group":  "Prod-US",
        "subscription_guid":  "c2771d27-bbec-81d3-855b-299988aa34a4",
        "token":  "?sv=2017-04-17\u0026sig=HlPoAp61WxsfjAcWAnF4xqBpMHuCbij8kRT2pwisL28%3D\u0026se=2018-04-29T20%3A44%3A01Z\u0026srt=sco\u0026ss=t\u0026sp=rl",
        "resource_uri":  "https://proddiag228.table.core.windows.net/"
    }
]  

14. Upload the generated file named cloudability-SAStokens-<DATETIME>.json to Cloudability.

15. Allow time for the credentials to validate. In the meantime, you will see the following state under Advanced Features.

16. When credentials are active in our system, the state will change to the below.

 

Note if you completed upload of your SAS tokens greater than 24 hours ago and are still not seeing your credentials as active in our app, we may ask that you send us the log file sas-token-script-logs-<DATETIME>.txt which will be in the same folder as the cloudability-SAStokens-<DATETIME>.json file.