Connect Azure account
Securely connect your Microsoft Azure account to Sedai's autonomous cloud platform.
If you do not have access to create a subscription in Azure, we recommend raising a ticket with your security team.
Summary: Sedai currently supports Azure Virtual Machines, Managed Disks, Databricks, and Azure Kubernetes Service (AKS).
You can integrate your Azure account either by creating a new application in your account or via multi-tenant service principal. These steps need to be repeated for each Azure account you want to connect to Sedai.
Set Up Azure AD Service Principal (Azure Portal)
Azure Client Credentials: Create a new application and provide the following information to connect to Sedai:
Subscription ID
Tenant ID
Client ID
Client Credentials
Multitenant Service Principal: Use an application created in Sedai’s Azure account. Sedai will use your Client ID and Client Credentials from Sedai’s Azure account to access your APIs. You will need to create a new service principal using Sedai’s application and provide the following information to connect to Sedai:
Tenant ID
Client ID
Connect Azure integration to Sedai

Sedai individually connects to Kubernetes clusters, so AKS clusters are displayed independent of their corresponding Azure account. To connect your AKS workloads, we recommend deploying Sedai's Smart Agent within your cluster, but you can also setup with agentless access.
Set Up Azure AD Service Principal
Note: In Sedai, each Subscription ID is treated as a unique Account. Therefore, you cannot add multiple Sedai accounts with identical Subscription ID and Tenant ID. If you have multiple resource groups under a single Subscription ID that require monitoring, adding that Subscription ID as a single Sedai account will meet your needs. This holds true while using Azure client credentials or Multi tenant service principal.
Log in to your Azure portal and setup access using one of the following options:
Azure Client Credentials: Create a new application and provide the following information to connect to Sedai: – Subscription ID
– Tenant ID – Client ID – Client Credentials
Multitenant Service Principal: Use an application created in Sedai’s Azure account. Sedai will use your Client ID and Client Credentials from Sedai’s Azure account to access your APIs. You will need to create a new service principal using Sedai’s application and provide the following information to connect to Sedai: – Subscription ID – Tenant ID
Once completed, navigate to https://yourcompany.sedai.app and click Connect Cloud to integrate your account within Sedai.
Integrate via Azure Client Credentials
In this approach, you will need to create and register a new single tenant application. (Note: Redirect URL is not required).
Client & Tenant IDs: Once application is created, go to its Overview page and copy and save the Client ID and Tenant ID; you will paste these into Sedai’s UI momentarily.
Subscription ID: Navigate to Subscriptions and copy the Subscription ID.
Secret Key: Navigate to your new application and go to Certificates & secrets. Generate a new secret key and copy the value.
Role Assignment at Subscription Level: Next, navigate to Access control and create a new role assignment and select Monitor Reader for the Job function role. Assign access to User, group, or service principal and click Select members to attach your newly created application to the assignment.
Role Assignment at Resource Group Level. Next, navigate to Access control under the required resource group and create a new role assignment and select Monitor Reader for the Job function role. Assign access to User, group, or service principal and click Select members to attach your newly created application to the assignment. Add role assignment in resource group Select Monitor Reader
Integrate via Multitenant Service Principal
If you're interested in using this approach, contact [email protected] to request an application hosted in Sedai's Azure account.
Create Service Principal: Contact our team to request an Application/Client ID.
Role Assignment: Navigate to Access control and create a new role assignment and select Reader for the Job function role. Assign access to User, group, or service principal and click Select members to attach Sedai’s application to the assignment.
Share Subscription & Tenant IDs with Sedai Team: Once you have created the new service principal and configured role assignment, copy the Subscription ID and Tenant ID and send them to our team who will complete setup within your Sedai environment.
Databricks Workspace Setup
Add Permissions to SP in Unity Catalog Metastore (Databricks Account Console)
Click User management > Service principals:
Select and add the Service Principal
Add permissions for the SP in the Databricks workspace
Settings > Identity and access
Groups (Add the SP to the ‘admins’ group)
System tables: Grant SELECT and USE SCHEMA to system.billing, system.compute
Connect Azure resource to Sedai
VM, DISK, Blob, Kubernetes
Log in to your Sedai account and navigate to Settings > Integrations.
Select Connect Cloud > Microsoft Azure
Select Resource types (either VM, DISK, Blob or Kubernetes resource.
Add Nickname for Account
Enter Azure Account Details
Test Connection to verify your connection works. If the connection fails, please double-check that you've entered the correct information in each field.
Connect a monitoring data source.
Since you can add multiple Azure accounts to Sedai, you will be asked to give your integration a unique nickname — this helps you easily identify resources within Sedai.
Databricks
Log in to your Sedai account and navigate to Settings > Integrations.
Select Add Integration > Databricks Account > Azure Databricks Account
Enter Azure Account details (nickname,subscriptionID) and select one of the following Onboarding Flows
Onboard Databricks Account: Faster, requires 'Account Admin' role in the databricks account. Required credentials
Onboard Databricks Workspace: Slower, each workspace has to be manually added and details such as have to be entered. Required credentials
Configure SQL Warehouse Access: Choose one of the following:
Option 1: Use Existing SQL Warehouse/Create a SQL Warehouse
Ensure it is Serverless
Recommended setting:
Cluster Size: X-Small
Autoscaling: 1-8
Assign the SP: ‘Can Manage’ permissions
Option 2: Let Sedai Create a Warehouse
Serverless config:
Auto-stop after 10 minutes
Cluster Size: Small
Autoscaling: 1-8
SP needs:
'Can Manage' SQL Warehouse permission
USE CATALOG and SELECT on system schema
Validation: Click “Test Warehouse” to verify access.
Connect a monitoring data source.
Last updated
Was this helpful?

