# Azure Marketplace Quickstart

This guide walks you through purchasing AGENTIC STAR from Azure Marketplace and completing the deployment. Simply enter your configuration values in the purchase form, and the entire process — from infrastructure provisioning to application installation — is handled automatically.

## Prerequisites

- An Azure subscription
- **Contributor** role or higher on the subscription
- **Required Resource Providers registered in the subscription** (see below)
- **Sufficient vCPU quota** (see below)

> **note**
>
> No prior setup of an AKS cluster or Helm is required. All infrastructure is automatically provisioned at purchase time.

### Required Azure Resource Providers

Deploying this product requires the following Resource Providers to be **registered in advance** on your subscription. If any are unregistered, the deployment will fail with errors like `MissingSubscriptionRegistration` after 10–20 minutes.

| Resource Provider               | Purpose                                             |
| ------------------------------- | --------------------------------------------------- |
| `Microsoft.Resources`           | ARM Template foundation (typically auto-registered) |
| `Microsoft.Authorization`       | Role assignments (RBAC)                             |
| `Microsoft.ManagedIdentity`     | User-Assigned Managed Identity                      |
| `Microsoft.Network`             | VNet / Subnet / NSG / Public IP                     |
| `Microsoft.Compute`             | VMSS backing AKS nodes                              |
| `Microsoft.ContainerService`    | AKS cluster                                         |
| `Microsoft.ContainerInstance`   | ACI used for the Deployment Script at deploy time   |
| `Microsoft.Storage`             | Storage Accounts (Private / Public)                 |
| `Microsoft.DBforPostgreSQL`     | PostgreSQL Flexible Server                          |
| `Microsoft.OperationalInsights` | Log Analytics Workspace                             |
| `Microsoft.Insights`            | Container Insights / Data Collection Rules          |
| `Microsoft.CognitiveServices`   | Azure AI Services (Content Safety / PII)            |

#### Check Registration Status

```bash
# Show the registration state for the relevant providers
az provider list --query "[?contains(['Microsoft.Resources','Microsoft.Authorization','Microsoft.ManagedIdentity','Microsoft.Network','Microsoft.Compute','Microsoft.ContainerService','Microsoft.ContainerInstance','Microsoft.Storage','Microsoft.DBforPostgreSQL','Microsoft.OperationalInsights','Microsoft.Insights','Microsoft.CognitiveServices'], namespace)].{Provider:namespace, State:registrationState}" -o table
```

#### Register Missing Providers

```bash
# Register individually
az provider register --namespace Microsoft.ContainerInstance
az provider register --namespace Microsoft.Storage
az provider register --namespace Microsoft.Compute
# ... repeat for any other unregistered providers
```

`az provider register` is idempotent — already-registered providers are a no-op. Registration can take several minutes; wait until every provider is in the `Registered` state before starting the deployment.

### vCPU Quota

AKS nodes can only be created within your subscription's vCPU quota (a limit per VM family plus a regional total). If the quota is too low, nodes cannot be added and the application installation stops partway through. In that case the deployment fails after more than an hour, and the error shows only a generic Azure message. Before you start the deployment, make sure the following quota is available in the target region.

| Quota                           | Required                                                                          |
| ------------------------------- | --------------------------------------------------------------------------------- |
| **Standard EDSv5 Family vCPUs** | At least 12, recommended 16 (3–4 nodes of the default VM size Standard\_E4ds\_v5) |
| **Total Regional vCPUs**        | At least the same amount                                                          |

- This is what the installation of the application suite needs. As agent executions grow, the autoscaler adds nodes, so leave headroom according to your workload
- If you select a VM size other than the default (such as Standard\_D4ds\_v4) in AKS Advanced Settings, secure the same amount in that family (for example, Standard DDSv4 Family vCPUs). Quota increase requests for some families are not approved automatically. If your request is not approved, use the default Standard\_E4ds\_v5
- PostgreSQL Flexible Server does not consume this quota

#### Check the Quota

```bash
# Show usage and limits in the target region (example: Japan East)
az vm list-usage --location japaneast -o table
```

In the rows `Standard EDSv5 Family vCPUs` and `Total Regional vCPUs`, confirm that `Limit` minus `CurrentValue` is at least the required amount.

#### Increase the Quota

In the Azure Portal, open **Quotas** → **Compute**, select the family and region, and request a new limit. If it is approved automatically, it takes effect within minutes. If it is not approved automatically, create a support request from the same screen.

## Steps

### 1. Select the AGENTIC STAR Advanced plan on Azure Marketplace

Search for "AGENTIC STAR" on [Azure Marketplace](https://azuremarketplace.microsoft.com/), open the offer, select the "AGENTIC STAR Advanced" plan, and click **\[Create]**.

![AGENTIC STAR offer page](https://developers.fd.agenticstar.tm.softbank.jp/en/assets/images/quickstart-azure-offer-898299e06ccad0b28bd37f9084233922.png)

### 2. Basics

Enter the standard Azure basic settings.

| Field              | Description                                           |
| ------------------ | ----------------------------------------------------- |
| **Subscription**   | The Azure subscription to deploy to                   |
| **Resource group** | Create a new one or select an existing resource group |
| **Region**         | The deployment region                                 |

### 3. General

| Field                      | Description                                | Default       | Constraints                                                                                                                                                                 |
| -------------------------- | ------------------------------------------ | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Environment Name**       | Identifier for the environment             | `agenticstar` | 3–21 characters, starts with a lowercase letter, lowercase alphanumeric and hyphens                                                                                         |
| **Managed Identity Name**  | Name of the managed identity               | `agtstr-id`   | 3–128 characters, lowercase alphanumeric and hyphens                                                                                                                        |
| **AKS Cluster Name**       | Name of the AKS cluster                    | `agtstr-aks`  | 3–63 characters, lowercase alphanumeric and hyphens                                                                                                                         |
| **Administrator Email**    | Email address of the initial administrator | —             | Valid email address                                                                                                                                                         |
| **Administrator Password** | Password for the initial administrator     | —             | 12–128 characters, must include at least one uppercase letter, one lowercase letter, one digit, and one special character. Only `@$!%*?&` can be used as special characters |
| **Primary Language**       | UI display language                        | Japanese      | Japanese / English / Français / Español / ไทย / العربية / Bahasa Indonesia / 中文（简体） / 中文（繁體） / Português (Brasil) / Deutsch / Italiano / Tiếng Việt / 한국어                   |

### 4. PostgreSQL Settings

| Field                            | Description                     | Default            | Constraints                                                                                                                                                                 |
| -------------------------------- | ------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **PostgreSQL Admin Username**    | Database administrator username | —                  | 1–63 characters, starts with a letter, letters, digits, and `_` only, cannot start with `pg_`                                                                               |
| **PostgreSQL Admin Password**    | Database administrator password | —                  | 12–128 characters, must include at least one uppercase letter, one lowercase letter, one digit, and one special character. Only `@$!%*?&` can be used as special characters |
| **PostgreSQL VM Size**           | Server specification            | Standard\_D2ds\_v4 | See below                                                                                                                                                                   |
| **PostgreSQL High Availability** | High availability mode          | Disabled           | See below                                                                                                                                                                   |

**PostgreSQL VM Size Options**

| Size               | Specification       | Use Case                                |
| ------------------ | ------------------- | --------------------------------------- |
| `Standard_D2ds_v4` | 2 vCPU / 8 GiB RAM  | Development and testing environments    |
| `Standard_D4ds_v4` | 4 vCPU / 16 GiB RAM | Small to medium production environments |
| `Standard_D8ds_v4` | 8 vCPU / 32 GiB RAM | Large production environments           |

**High Availability Options**

| Mode               | Description                                                       |
| ------------------ | ----------------------------------------------------------------- |
| **Disabled**       | No HA (lowest cost)                                               |
| **Same Zone**      | Replica within the same zone                                      |
| **Zone Redundant** | Zone-redundant (recommended for production; doubles compute cost) |

### 5. AKS Advanced Settings (Optional)

Check **"Customize AKS Advanced Settings"** to reveal detailed AKS node pool settings. In most cases, the default settings are sufficient.

> **caution**
>
> The default Standard\_E4ds\_v5 is the minimum working configuration. If you change the VM size, secure the [vCPU quota](#vcpu-quota) for that family first.

**System Pool**

| Field                  | Default            | Range / Options                                              |
| ---------------------- | ------------------ | ------------------------------------------------------------ |
| Node Count             | 1                  | 1–20                                                         |
| Min Count (Autoscaler) | 1                  | 1–20                                                         |
| Max Count (Autoscaler) | 8                  | 1–100                                                        |
| VM Size                | Standard\_E4ds\_v5 | Standard\_E4ds\_v5 / Standard\_D4ds\_v4 / Standard\_D8ds\_v4 |

**User Pool**

| Field                  | Default            | Range / Options                                              |
| ---------------------- | ------------------ | ------------------------------------------------------------ |
| Node Count             | 1                  | 1–50                                                         |
| Min Count (Autoscaler) | 1                  | 1–50                                                         |
| Max Count (Autoscaler) | 10                 | 1–100                                                        |
| VM Size                | Standard\_E4ds\_v5 | Standard\_E4ds\_v5 / Standard\_D4ds\_v4 / Standard\_D8ds\_v4 |

**Availability Zones**

| Field              | Default     | Options                                 |
| ------------------ | ----------- | --------------------------------------- |
| Availability Zones | Zones 1 & 2 | Zones 1 & 2 / Zones 1 & 3 / Zones 2 & 3 |

The two zones apply to both node pools. Depending on your subscription and region, some zones may not accept VMs. If the deployment fails with `AvailabilityZoneNotSupported`, select a different combination and try again.

### 6. Datadog Integration (Optional)

Check **"Enable Datadog Integration"** to reveal the Datadog integration settings.

| Field                       | Description                                |
| --------------------------- | ------------------------------------------ |
| **Datadog API Key**         | Your Datadog API key                       |
| **Datadog Application Key** | Your Datadog application key               |
| **Datadog Site**            | Datadog site (AP1 / US1 / US3 / US5 / EU1) |

### 7. Review and Deploy

Review all settings and click **\[Create]** to start the deployment.

The deployment automatically creates the following resources:

- **AKS Cluster** (System Pool + User Pool with autoscaler)
- **PostgreSQL Flexible Server** (v16, with extensions such as pgvector pre-installed)
- **Storage Accounts** (two: one private and one public)
- **Virtual Network / NSG** (network isolation pre-configured)
- **Log Analytics Workspace** (Container Insights integration enabled)
- **Azure AI Services**
- **AGENTIC STAR application suite** (automatically installed via Helm charts)

> **info**
>
> Deployment takes approximately 1 hour. You can monitor progress on the Azure Portal deployment page.

> **caution**
>
> If the deployment fails, see the [Deployment Troubleshooting Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/build/guide/troubleshooting-guide.md). Do not redo the installation by hand on the failed environment. Fix the cause, then delete the managed application and create it again.

## After Deployment

### Verifying the Deployment

When the deployment succeeds, every component is installed as a Helm release. Connect to the cluster and check the following.

```bash
# Connect to the cluster (the resource group is the managed resource group of the managed application; its name starts with mrg-)
az aks get-credentials --resource-group <managed resource group> --name <AKS Cluster Name>

# All 25 Helm releases are deployed
HELM_DRIVER=configmap helm list -A

# No pods other than Running / Completed
kubectl get pods -A | grep -v -E 'Running|Completed'

# The initial setup job (init-platform) is Complete
kubectl get jobs -n librechat-auth
```

> **note**
>
> The marketplace edition uses configmap as the Helm storage driver. Without `HELM_DRIVER=configmap`, `helm list` shows nothing.

If any of these checks fails, see the [Deployment Troubleshooting Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/build/guide/troubleshooting-guide.md).

### Checking Access IP Addresses

Once deployment is complete, check the IP addresses for each application. AGENTIC STAR creates 4 LoadBalancer services for different purposes.

```bash
kubectl get svc -n ingress-nginx -o wide | grep LoadBalancer
```

| Service Name           | Purpose          | Access URL              |
| ---------------------- | ---------------- | ----------------------- |
| `ingress-nginx-front`  | Main application | `https://<EXTERNAL-IP>` |
| `ingress-nginx-admin`  | Admin console    | `https://<EXTERNAL-IP>` |
| `ingress-nginx-extapi` | API endpoint     | `https://<EXTERNAL-IP>` |

> **note**
>
> The login page (`ingress-nginx-auth`) is intentionally omitted: due to how OAuth redirects work, opening it directly does not produce a working post-login navigation. **Always start from the main application URL** — the login page is invoked automatically when authentication is required.

Since self-signed certificates are used, your browser will display certificate warnings. Accept the warning to proceed on first access.

> **tip**
>
> To configure custom domains, register each LoadBalancer IP address in your DNS using A records. See the [Domain Settings Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/build/guide/domain-guide.md) for details.

> **Cloud-Specific Differences**
>
> Azure Standard Load Balancer assigns a static Public IP, so the `EXTERNAL-IP` column shows an IP address directly. The AWS Marketplace edition uses Network Load Balancers, which return an ELB DNS name instead, and DNS records must be configured as CNAMEs rather than A records. See the [AWS Marketplace Quickstart](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/build/quickstart/quickstart-aws.md) for details.

### Logging In

![Admin console login](https://developers.fd.agenticstar.tm.softbank.jp/en/assets/images/quickstart-azure-login-108aae8054b69f8c894a8f26185b314a.png)

Access the admin console IP address in your browser and log in with the **Administrator Email** and **Administrator Password** you entered in the purchase form.

As a next step, perform the initial setup in the admin console. See the [Settings Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/build/guide/settings-guide.md) for details.

To start using the API, see the [Marketplace API Quickstart](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/api/quickstart/call-api.md).
