Install Pointer on AKS

Pointer runs your finance and operations procedures on your own Azure Kubernetes Service (AKS) cluster. It uses your Azure OpenAI account for model calls and Microsoft Entra ID for sign-in. Pointer keeps its data in Azure resources you own, in your subscription.

How you buy

Pointer has one public plan at a list price of $2 per agent minute. Pointer can send a private offer to your Azure billing account to set your rate. Find your billing account ID in Cost Management + Billing under Settings → Properties and share it with Pointer. Your billing administrator accepts the offer in Private Offer Management. Use a subscription under that billing account.

Microsoft bills monthly in arrears for the agent minutes each Marketplace install reports every hour. An agent minute is a minute a procedure run spends working. Time waiting for a person and test modes such as dry runs are excluded. Billable usage on every install counts, including a test install. Azure bills your resources and Azure OpenAI usage separately.

Pointer will confirm the private offer steps and how the plan rate appears in the portal during the first Marketplace Preview install.

What you need

  • AKS and networking. Use a subscription that allows Marketplace purchases and a region that supports Azure Marketplace Kubernetes apps. Use one Pointer install per cluster. Use a separate cluster for a test install. Plan for about four Linux AMD64 nodes, each with 8 vCPU and 32 GiB memory. Turn on the autoscaler with a minimum of two and a maximum of at least five nodes. Enable the AKS OIDC issuer and Workload Identity. Use Azure CNI Overlay with Cilium and record the VNet, gateway subnet, pod and Service ranges.
  • Database and cache. Use private networking and DNS for Azure Database for PostgreSQL flexible server and Azure Managed Redis. Use PostgreSQL 17 with TLS, max_connections set to 500, and VECTOR and BTREE_GIN on the extension allowlist. Make the Pointer database and its owner user. Grant that user ALL on schema public in each database you create for Pointer and its bundled Temporal. Set Redis to NoCluster and NoEviction with TLS and access keys enabled.
  • Storage. Create a private Blob container. In the Blob account's CORS settings, allow the Pointer app's origin, methods GET, HEAD, and PUT, and all request headers. Expose ETag and Content-Type. Create an NFS share in a separate Premium Azure Files account. Turn off required secure transfer for the NFS account, allow only the AKS node subnet, and leave root squash off so the workspace init container can set ownership.
  • Signing key and models. Create an RSA 2048 key in Key Vault with sign and verify operations. Set up model deployments on your Azure OpenAI account. Keep the Azure resources in the same subscription and region.
  • Gateway. Set up Application Gateway for Containers with its ALB controller and an HTTPS Gateway listener that accepts routes from the pointer namespace and supports WebSockets. Use a TLS certificate from a public CA that your AKS nodes and Pointer pods trust. Point your host's DNS record at the gateway frontend.
  • App identities. Create two user-assigned managed identities and federate them to the backend and worker service accounts in the pointer namespace: pointer-backend and pointer-worker. Grant both Storage Blob Data Contributor on the container, Storage Blob Delegator on the account, and Cognitive Services OpenAI User on the Azure OpenAI account. Grant the backend Key Vault Crypto User on the signing key. Your cloud team needs Owner, User Access Administrator, or Role Based Access Control Administrator to grant these roles.
  • Entra sign-in. Create an Entra app registration in the subscription's tenant and create a client secret. Set its web redirect URI to https://<host>/api/auth/sso/oidc/callback. Make sure the ID token includes an email claim. Populate each user's Mail attribute or add email as an optional ID token claim under Token configuration. Choose two administrators who use your organization's work email domain.
  • Installer roles. The installer needs Contributor or Owner on the subscription, Kubernetes Extension Contributor on the AKS cluster, and Reader on its resource group.

The first Marketplace Preview install will confirm regional availability for the extension and whether the installer can deploy with these Azure roles alone.

Install Pointer

Pointer has tested the package's Helm chart on AKS. The first Marketplace Preview install still needs to confirm the portal entry points, form screens and how Azure passes the form values to Pointer.

  1. In the Azure portal, search for Pointer in Marketplace under Containers, or open your AKS cluster and go to Extensions + applications → Add and search for Pointer there.
  2. Open the offer, check your rate under Plans + Pricing, and select Create.
  3. Use the following values to complete the form.

Basics

Subscription, Resource group
Select the subscription and resource group that contain your AKS cluster.
AKS cluster
Select the existing cluster where Pointer will run.
Install name
Choose 6 to 30 lowercase letters and digits. The default is pointer. It names the extension and its release.

Database and cache

PostgreSQL server
Copy your flexible server hostname, ending in .postgres.database.azure.com.
Database name
Enter pointer, the database your Azure team created.
Database user
Enter pointer, the user that owns the database.
Database password
Enter the password your Azure team set for the database user.
Azure Managed Redis host
Copy the Redis hostname, ending in .redis.azure.net.
Redis access key
Copy an access key from the Azure Managed Redis resource.
Install Temporal with Pointer
Keep this on to use the bundled Temporal. Grant the database user CREATEDB or have it own pre-created temporal and temporal_visibility databases.
Temporal address
If you turn off bundled Temporal, enter your server address as host:port. Use a server with a pointer namespace and a connection without TLS or a client certificate.

Storage

Blob storage account
Enter the name of your Azure Blob Storage account.
Blob container
Enter app-data, the private container your Azure team created.
Azure Files resource group
Enter the resource group of your Premium Azure Files account.
Azure Files account
Enter the name of that Premium Azure Files account.
NFS share
Enter pointer-fs, the NFS share your Azure team created.
Folder in the share
Enter pointer, the directory owned by user and group 1000.

Identity and AI models

Backend identity client ID
Copy the client ID from the backend managed identity.
Worker identity client ID
Copy the client ID from the worker managed identity.
Key Vault signing key
Copy the full ID of the oidc-signing key from Key Vault, including the version.
Azure OpenAI endpoint
Copy your account endpoint as https://<account>.openai.azure.com/ with the trailing slash.
Model deployments
Use the model and deployment names from Azure OpenAI. Enter comma-separated model=deployment pairs. Use *=deployment to provide a default.

Network and sign-in

Host name
Enter the lowercase DNS name your Azure team pointed at the gateway. Enter only the host. The app and its /api path share it.
Gateway name, Gateway namespace
Copy both values from your Kubernetes Gateway.
Gateway subnet
Copy the address range of the gateway subnet from your VNet.
Virtual network range
Copy the CIDR range of your cluster’s Azure virtual network.
Pod range
Copy the pod CIDR from the AKS cluster’s network profile.
Service range
Copy the Service CIDR from the AKS cluster’s network profile.
Sign-in app client ID
Copy the application (client) ID from your Entra app registration.
Sign-in app client secret
Enter the client secret value from the same registration.
Workspace name
Choose a name for your first Pointer workspace.
Email domain
Enter your organization’s work email domain.
First administrator, Second administrator
Enter the work email addresses of your two first platform administrators.

Email

Send email
Choose No or By SMTP.
SMTP host, SMTP port, SMTP user, SMTP password, Sender address
If you choose By SMTP, enter the server, port, credentials, and sender your mail team provided. Port 465 uses TLS from the start of the connection.

Password fields require at least eight characters, including at least one character other than a digit. They reject commas, backslashes, braces and square brackets.

Select Review + create, then Create. The extension is expected to create the pointer namespace and install a release named after the install name. In Extensions + applications, check that Provisioning State shows Succeeded. The first Preview install will confirm this behavior.

After installation, set the namespace's Pod Security enforcement, audit, and warning levels to baseline. Allow up to 30 minutes for the first database migration. When it finishes, open https://<host>/api/health and check that it returns HTTP 200.

Sign in for the first time

Open your Pointer host and have both named administrators sign in. Pointer grants both platform administrator roles after both have signed in. Microsoft Entra ID may ask new users to register a multifactor authentication method on first sign-in.

Outbound destinations

Use this list to plan your network rules. Marketplace installs start with the app chart's egress policy off, so the backend and worker can reach the node's Instance Metadata Service unless your own rules block them. Sandbox and desktop pods have separate rules.

  • Data services. Allow PostgreSQL on TCP 5432, Managed Redis on TCP 10000 with TLS, and the node subnet to the Azure Files NFS share on TCP 2049. Allow HTTPS to your Blob endpoint (<account>.blob.core.windows.net) from Pointer and users' browsers, and to Key Vault (<vault>.vault.azure.net) from the backend.
  • App and identity. Allow HTTPS to your gateway host, the AKS API server for the worker, login.microsoftonline.com, and your Azure OpenAI endpoint (<account>.openai.azure.com, which also resolves under *.cognitiveservices.azure.com).
  • Optional connections. Allow your SMTP server on the configured port, external Temporal on its configured port, and the integration endpoints your procedures use. Sandbox and desktop pods can reach the internet on TCP 80 and 443 according to their network tier. Block their access to your VNet, pod and Service ranges, Instance Metadata Service, and Azure WireServer.
  • Marketplace billing. The meter job needs HTTPS to marketplaceapi.microsoft.com and TCP 80 to the node's Instance Metadata Service (169.254.169.254) for its identity token.
  • Marketplace extension. Allow HTTPS to arcmktplaceprod.azurecr.io and arcmktplaceprod.<region>.data.azurecr.io for Pointer images, and mcr.microsoft.com and *.data.mcr.microsoft.com for Azure's agent images. The extension agent needs HTTPS to <region>.dp.kubernetesconfiguration.azure.com, *.ingestion.msftcloudes.com, and *.microsoftmetrics.com.

The first Marketplace Preview install will confirm the registry pulls, extension agent traffic, and whether the meter job can authenticate and report usage. It will also confirm whether changing app.networkPolicy.egress in the extension updates the deployed policy. Verify the policy on your cluster before relying on it.

Uninstall

In the Azure portal, open the AKS cluster and select Extensions + applications. Select the Pointer install and choose Uninstall. Your data stays in your Azure resources. If you plan to reinstall, preserve the pointer-app-secrets Secret and reuse the install name. Pointer needs the original encryption key to read stored credentials.

The first Marketplace Preview install will confirm that uninstalling stops the meter job and future Pointer usage charges, and that the extension leaves the Secret in place. Azure still bills for usage already reported and for resources you keep.

Contact

For pricing or install questions, email team@pointer.ai or contact Pointer.