> For the complete documentation index, see [llms.txt](https://docs.lightbeam.ai/lxqobxw6ak7CTnsQjikH/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lightbeam.ai/lxqobxw6ak7CTnsQjikH/getting-started/installer-guides/platform-specific/microsoft-azure.md).

# Microsoft Azure

***

{% hint style="info" %}
**LightBeam Installation:**

Before proceeding with the steps in this guide, ensure you have gone through the [LightBeam Installation process](https://docs.lightbeam.ai/lxqobxw6ak7CTnsQjikH/installer-guides/lightbeam-installer). Familiarize yourself with the installation prerequisites and steps to ensure a smooth setup.
{% endhint %}

### Overview <a href="#heading-h.odhhbva7an79" id="heading-h.odhhbva7an79"></a>

### 1.0 Setup Overview <a href="#heading-h.rr931ma1w7ez" id="heading-h.rr931ma1w7ez"></a>

* There are two scenarios when deploying the LightBeam application:
  * The **AKS (Azure Kubernetes Service)** cluster is already present on the customer account.
  * The **AKS cluster** is to be deployed by LightBeam.
* This pre-setup is required only for the second scenario.

{% hint style="info" %}
**Note:** We may ask Azure to launch a Jump Box VM with internet access in some cases.
{% endhint %}

### 1.1 Create and Set Up a Jump Box VM <a href="#heading-h.uzua2w90xh3a" id="heading-h.uzua2w90xh3a"></a>

Create a micro instance (**Ubuntu OS**) to use as a Jump Box VM to configure and access the AKS clusters.

{% hint style="info" %}
**Note:** Verify that the deployed Jump Box VM has internet access (confirm that firewall rules allow outbound traffic).
{% endhint %}

#### Set up the Jump Box VM <a href="#heading-h.y5znrhj1nkj5" id="heading-h.y5znrhj1nkj5"></a>

1. **Install `unzip` package:**
   * `sudo apt-get update`
   * `sudo apt-get install unzip`<br>
2. **Install `Kubectl CLI:`**
   * `curl -LO "https://dl.k8s.io/release/`**`$(`**`curl -L -s https://dl.k8s.io/release/stable.txt`**`)`**`/bin/linux/amd64/kubectl"`
   * `chmod +x kubectl`
   * `mv kubectl /usr/local/bin/`
   * `kubectl version`<br>
3. **Install `Helm CLI:`**
   * Download the release from here: [`https://get.helm.sh/helm-v3.3.4-linux-amd64.tar.gz`](https://get.helm.sh/helm-v3.3.4-linux-amd64.tar.gz)
   * Run the following commands:
     1. `tar -xvf` [`helm-v3.3.4-linux-amd64.tar.gz`](https://get.helm.sh/helm-v3.3.4-linux-amd64.tar.gz)
     2. `mv linux-amd64/helm /usr/local/bin/`

***

### 2.0 Deploying LightBeam Platform in Microsoft Azure Cloud <a href="#heading-h.9twr2w9jzpmg" id="heading-h.9twr2w9jzpmg"></a>

#### Creating AKS cluster <a href="#heading-h.zgkyq7ve7ji9" id="heading-h.zgkyq7ve7ji9"></a>

i) Login to the [`Azure portal`](https://azure.microsoft.com/en-gb/) and search for “*Kubernetes services*”.

<img src="/files/gJB2tq7W6FKBrrLilRRB" alt="Figure 1. Microsoft Azure Portal - Kubernetes Services
" width="563">

ii) Click on **Kubernetes services.** You will see the following page:

![Figure 2. Create Kubernetes Cluster
](/files/WnlceV9lhJT6nzfD4Bi4)

iii) Click on **Create Kubernetes cluster.**<br>

iv) Provide **Kubernetes cluster name**. Give the same name to a resource group.

<img src="/files/CQlzwQvTl6UwPnP812j3" alt="Figure 3. Kubernetes cluster name
" width="563">

* Select a VM size. We recommend a node with resource **8vCPU** and **32 GB** memory per node.

<img src="/files/jqxNvs29TOLDnZNE8zXv" alt="Figure 4. Select a VM size" width="563">

* Once the instance type is selected, choose the **Manual** option for the *Scale* method.<br>

**Set node count as 3 (minimum standard performace) or 5+ ( higher performance recommended)**&#x20;

<img src="/files/69nr34RsOOAQMlTu4HVF" alt="Figure 5. Scale method
" width="375">

iv) Click on the **Review + Create** button.

<img src="/files/64Zy2l40DdzkNONRvz7V" alt="Figure 6. Click on ‘Review + create’
" width="375">

v) Once the validation is passed, click on the **Create** button which will start the AKS cluster deployment.

<img src="/files/pUjP13q9w3OlqWN7t2G5" alt="Figure 7. Click on ‘Create’
" width="353">

vi) Once the deployment is ready, the AKS cluster will be ready for access.<br>

<img src="/files/OUrpYkpczS3e1OCGyd6h" alt="Figure 8. Deployment progress
" width="563">

* Click on **Go To Resource** once the deployment is completed.

<figure><img src="/files/jHmh8PGY7Oz2C9H43sEo" alt=""><figcaption><p>Figure 9. Go To Resource</p></figcaption></figure>

vii) Click on **Connect.** This will open up the following window on the right side:<br>

<img src="/files/NrXA9vp54IdpwJWblRRs" alt="Figure 10. Connect to lb-cluster" width="295">

***

### 3.0 Access AKS Cluster <a href="#heading-h.7ga52r9i0dru" id="heading-h.7ga52r9i0dru"></a>

**Additional Setup** to access the AKS cluster from the local machine or VM running in Azure.<br>

***

### 4.0 Setup Azure CLI <a href="#heading-h.jwu8twhzd3ef" id="heading-h.jwu8twhzd3ef"></a>

To set up Azure CLI on your system:

[`https://docs.microsoft.com/en-us/cli/azure/install-azure-cli`](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli)<br>

***

### 5.0 Authenticate az CLI <a href="#heading-h.lhcdl8mag7n" id="heading-h.lhcdl8mag7n"></a>

To authenticate Azure CLI on your system:

[`https://docs.microsoft.com/en-us/cli/azure/authenticate-azure-cli`](https://docs.microsoft.com/en-us/cli/azure/authenticate-azure-cli)<br>

***

### 6.0 Run a few commands to validate <a href="#heading-h.3hlohlxj851k" id="heading-h.3hlohlxj851k"></a>

* `az account set --subscription <SUBSCRIPTION_ID>`
* `az aks get-credentials --resource-group <GROUP_NAME> --name <CLUSTER_NAME>`
* `kubectl get nodes`

{% hint style="info" %}
**Pre-requisites:** You need to install **Kubectl** and **Helm CLI** utilities.
{% endhint %}

***

### **Commands to create AKS cluster using Azure CLI**

```
// Considering you want to use an existing resource group called LightBeam_AKS

az extension add --name aks-preview; az extension update --name aks-preview
az feature register --namespace "Microsoft.ContainerService" --name "EnableAPIServerVnetIntegrationPreview"
az feature show --namespace "Microsoft.ContainerService" --name "EnableAPIServerVnetIntegrationPreview"
az provider register --namespace Microsoft.ContainerService

// Considering the cluster name is LightBeam-AKS-cluster

az aks create -n LightBeam-AKS-cluster -g LightBeam_AKS -l westus2 --enable-apiserver-vnet-integration --disable-private-cluster

az aks nodepool add --resource-group LightBeam_AKS --cluster-name LightBeam-AKS-cluster --name systempool --os-type AzureLinux --node-vm-size standard_d8s_v3 --node-count 1 --mode system

az aks nodepool add --resource-group LightBeam_AKS --cluster-name LightBeam-AKS-cluster --name userpool --os-type AzureLinux --node-vm-size standard_d8s_v3 --node-count 3 --mode user --max-pods 50

// Delete the default systempool created 
az aks nodepool delete --resource-group LightBeam_AKS --cluster-name LightBeam-AKS-cluster --name nodepool1
```

### 7.0 LightBeam Installation

Follow the installation instructions in the [LightBeam Installer guide](/lxqobxw6ak7CTnsQjikH/getting-started/installer-guides/core/lightbeam-installation-and-upgrade.md#_w3t1uru6c4f9).

Use the `--aks` flag in the installer command to specify the platform used is Azure AKS.

***

### About LightBeam <a href="#heading-h.4p6ohju0dnbe" id="heading-h.4p6ohju0dnbe"></a>

LightBeam automates Privacy, Security, and AI Governance, so businesses can accelerate their growth in new markets. Leveraging generative AI, LightBeam has rapidly gained customers’ trust by pioneering a unique *privacy-centric* and *automation-first* approach to security. Unlike siloed solutions, LightBeam ties together sensitive data cataloging, control, and compliance across structured and unstructured data applications providing 360-visibility, redaction, self-service DSRs, and automated ROPA reporting ensuring ultimate protection against ransomware and accidental exposures while meeting data privacy obligations efficiently. \
\
LightBeam is on a mission to create a secure privacy-first world helping customers automate compliance against a patchwork of existing and emerging regulations.

For any questions or suggestions, please get in touch with us at: <support@lightbeam.ai>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lightbeam.ai/lxqobxw6ak7CTnsQjikH/getting-started/installer-guides/platform-specific/microsoft-azure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
