Skip to content

Quick start

import { Steps } from “@astrojs/starlight/components”;

The fastest path from “I’m curious” to “an AI is answering my customers’ questions” is about 5 minutes of clicking and 5 more minutes of waiting for Azure to provision resources.

What you need

  • An Azure subscription in any region where Azure OpenAI is available (most are).
  • Owner or Contributor + User Access Administrator on that subscription (the deploy creates RBAC role assignments).
  • Microsoft Teams admin access in your tenant (one-time sideload of the Teams app).
  • A website where you can paste a <script> tag (for the widget).

If you don’t have admin on Teams or Azure, send your admin the install link — the install wizard prompts for everything they’ll need. For the full role-by-role list (Azure, Marketplace purchasing, Teams, Entra ID, OpenAI quota), see Prerequisites.

Five-minute walkthrough

  1. Pick a plan.

    On the Azure Marketplace listing, click Get It Now and choose Start (3 seats / $49), Growth (7 seats / $99), or Professional (15 seats / $199). All plans have a 7-day grace period if you cross your seat quota — you won’t be locked out the moment your team grows.

    This price is the plan license only. The stack deploys into your Azure subscription, so the Azure resources are a separate charge billed to you directly by Microsoft at cost (~$3–15 / ~$10–30 / ~$60–120 per month by plan, plus pay-as-you-go AI tokens). See Cost & billing.

  2. Run the deploy wizard.

    Azure opens our custom wizard. You’ll need:

    • Stack name — 3-12 lowercase letters + digits, e.g. acmesupport. Becomes the suffix on every resource name (Cosmos, Key Vault, Function App, etc.).
    • Region — pick one with Azure OpenAI; westus3 is a good default.
    • Allowed widget origins — your website domains, e.g. https://www.acme.com. Use * to allow any origin during evaluation.
    • Optional system prompt — shape the assistant’s tone. Leave blank for a helpful-generalist default.

    Click Review + CreateCreate. Deployment takes ~5 minutes.

  3. Set your admin key.

    A fresh deployment has no admin key yet — the dashboard and admin endpoints are open to anyone who knows your Function App hostname until you set one. Do this first:

    1. Open https://{customer-fa-host}/api/dashboard (find the hostname in the Managed Resource Group: the Function App named pocai-fa-…).
    2. In the Settings panel, click Rotate admin key.
    3. The new key is shown once. Copy it to your password manager.

    From that moment the dashboard and admin endpoints require the key (how the key works). If you ever lose it, rotate again from an open dashboard session — or see key recovery.

  4. Sideload the Teams app.

    First set up the AAD app for Teams SSO (a one-time script run plus a support request). Then, in your customer dashboard, click Teams setup. Step 2 downloads a per-deployment Teams .zip. Open Teams Admin Center, click Upload new app, and select the .zip. That’s it — your agents now see a PointOfContactAI tab in Teams.

  5. Embed the widget.

    Add this one line to your site’s footer (replace {customer-fa-host} with your Function App hostname — visible in the dashboard footer):

    <script src="https://{customer-fa-host}/api/widget.js" data-customer-endpoint="https://{customer-fa-host}" async></script>

    The data-customer-endpoint attribute is required — without it the widget logs a console warning and doesn’t mount. Refresh your page — a small chat bubble appears in the bottom-right. Click it; the assistant says hello. (Optional attributes →)

What you have now

  • An AI assistant answering visitors on your site.
  • A Teams tab where your agents can claim chats when AI alone isn’t enough.
  • A live dashboard at https://{customer-fa-host}/api/dashboard?code=<admin-key> showing token cost, active sessions, and seat usage.

Next