Skip to main content
Microsoft Azure

Learn how to use OneIQ Pulse to capture billing, configuration and performance metrics from Azure subscriptions.

Support Kappa avatar
Written by Support Kappa
Updated over a week ago

Overview

Use OneIQ Pulse to connect all Azure subscriptions to your IT environment in OneIQ, so that you can:

  • Optimize Azure spend by right-sizing Azure Virtual Machines with OneIQ Insights.

  • Understand dependencies among Azure and other workloads across Hybrid IT.

  • Identify cost-saving opportunities to repatriate application workloads from Azure to the datacenter.

Downloading OneIQ Pulse for Azure

OneIQ Pulse for Azure can be downloaded as an Azure Resource Manager (ARM) manifest from the Connectors tab of the IT environment in the OneIQ Portal:

  1. Login to the OneIQ Portal.

  2. Select IT Environments in the left navigation menu and go to the Connectors tab.

  3. Select Microsoft Azure as the platform to connect.

  4. In Connect your Microsoft Azure cloud, specify the name of the OneIQ Pulse for Azure connector to distinguish it from other connectors in your IT environment.

    For example, this could be the name of the Azure region. Then click Download to save the OneIQ Pulse ARM manifest.

  5. Go to the Azure Portal and search for Deploy a custom template.

  6. Select Build your own template in the editor.

  7. Load file.

  8. Select the downloaded OneIQ Pulse ARM manifest.

  9. Click Open and then Save.

  10. Create new resource group and select the desired Region.

  11. Credentials can be created with Azure CLI using an account with permissions to create Service Principals:


    First, authorize Azure CLI:
    az login

    Then execute the following commands:
    az ad sp create-for-rbac --role "Monitoring Reader" --name OneIQ-Pulse --scopes /subscriptions/{Azure Subscription ID}

    az ad sp create-for-rbac --role "Reservations Reader" --name OneIQ-Pulse --scopes /subscriptions/{Azure Subscription ID}

    The output will contain:

    • appId which is the Service Principal ID and

    • password which is the Service Principal Token.


    Note: When deploying OneIQ Pulse for Azure using newly generated credentials, remember that monitoring may not commence immediately, as some time is needed for changes to propagate across systems such as Azure Active Directory.

    For NetFlow data a Storage Blob Data Reader role will also be required:

    az role assignment create --assignee "Tennant ID" --role "Storage Blob Data Reader" --scope "/subscriptions/{Azure Subscription ID}

  12. Select the VM Size to deploy using guidelines below.

  13. Click Review + Create and ensure that the deployment is successful.

VM Sizing Guidelines

Each OneIQ Pulse for Azure connector can scale up to 100,000 containers and virtual machines. For deployment guidance in larger environments, please contact our team.

Containers + VMs

VM Size

vCPUs

Memory (GB)

Up to 5,000

Standard_B2s

2

4

5,000 - 9,999

Standard_B2ms

2

8

10,000 - 24,999

Standard_B4ms

4

16

25,000 ,49,999

Standard_B8ms

8

32

50,000 - 74,999

Standard_B12ms

12

64

75,000 - 99,999

Standard_B16ms

16

128

Did this answer your question?