---
title: Azure
slug: azure
docTags: 
createdAt: 2024-12-24T04:34:29.235Z
---

Connect Aiden with your Azure cloud platform to get intelligent assistance with resource management, infrastructure operations, and cloud optimization. Once enabled, Aiden becomes your Azure cloud expert, helping you manage resources through natural conversations.

## Capabilities

With Azure integration, Aiden can:

- Monitor and manage virtual machines and compute resources
- Track storage accounts and blob containers
- Analyze virtual network configurations
- Review Azure Active Directory settings
- Investigate Azure Monitor metrics
- Optimize cloud resource utilization
- Analyze Azure billing and costs

## Custom Skills

On top of the several out of the box capabilities, you can create custom skills to add additional capabilities. See the [Skills](https://docs.opsverse.io/6TWO-overview) page for more information.

## Example Interactions

- `Show me all storage accounts in the development resource group`
- `What's our current Azure spending trend?`
- `Stop all non-production VMs in East US`
- `Check if any AKS clusters are running outdated versions`
- `List virtual networks with overlapping address spaces`

## Prerequisites

To integrate with Aiden, provide credentials like `Client ID` , `Client Secret` , and `Tenant ID` associated with a service principal in your Azure cloud. The service principle should have a `Basic Reader` role attached to it.

Follow this official [Azure Documentation](https://learn.microsoft.com/en-us/cli/azure/azure-cli-sp-tutorial-1?tabs=bash) to create a service principal.

Use the Azure CLI or the [Bash Environment in Azure Cloud Shell](https://shell.azure.com/) to execute the following CLI command to create a service principal.

```shell
az ad sp create-for-rbac --name "opsverse-aiden-sp" --role Reader --scopes /subscriptions/<azure_subsription_id>
```

The output of the above command after execution will be as follows&#x20;

```shell
{
  "appId": "myAppId",
  "displayName": "myServicePrincipalName",
  "password": "myServicePrincipalPassword",
  "tenant": "myTentantId"
}
```

Use the `appId` as the `Client Id` , `password` as the `Client Secret` and the `tenant` as the `Tenant Id` to configure the Azure Integration with Aiden.

## Configuration Steps

1. Navigate to **Integrations** in the sidebar
2. Locate the Azure integration card and click **Activate**
3. Configure your Azure credentials:&#x20;
   - `Client ID`
   - `Client Secret`
   - `Tenant ID`
4. Click **Save** to enable the integration

::Image[]{src="https://api.archbee.com/api/optimize/A1ybFzEd4Yg88MHjQbQjT-iCNfGFJ-g-3vf4IPtnfGB-20241230-203815.png" size="80" width="2880" height="1188" position="center" showCaption="false"}

## Security Best Practices

- Create a dedicated service principal for Aiden
- Implement least-privilege access using Azure RBAC
- Regularly rotate client secrets
- Monitor Aiden's activities through Azure Activity Logs

***Note:&#x20;****Ensure your Azure service principal has appropriate RBAC permissions for the tasks you want Aiden to perform.*