Skip to content
Point of Contact

How updates reach your stack

Your stack runs two kinds of software, updated through two different channels.

Customer-runtime updates (the code in your Function App)

We (the publisher) ship these — no action from you:

  1. We upload the new runtime package (released-package.zip) into your Function App’s deployment storage container, using the publisher Contributor access on the Managed Resource Group.
  2. We tell the Functions host to re-sync, which mounts the new package and re-registers the functions.
  3. We probe your stack’s /api/health until it answers on the new version.

Impact during an update: the Functions host reloads briefly — an in-flight request can see a few seconds of extra latency; there is no data migration and nothing in Cosmos, Key Vault, or SignalR is touched. Visitors’ widget sessions live in their browser (localStorage) and in Cosmos, so open conversations survive the reload.

Every update we perform is visible in your Activity Log under the publisher principal (see How to verify).

How to check which version you’re running

Requesting or deferring an update

There is no customer-facing update toggle today. If you read about a fix in the changelog and your footer shows an older version, contact support with your stack name to request the update. If your change-management process needs an update deferred (e.g. a freeze window), tell support the window and we schedule around it.

Infrastructure changes (the Azure resources themselves)

The resources in the Managed RG (Cosmos, SignalR, Key Vault, OpenAI, Function App plan) are not changed by runtime updates. They change only when:

  • You change plan in the Marketplace — we PATCH plan settings (seat quota etc.) on your Function App within seconds, zero downtime. Details →
  • You request a configuration change through support (allowed origins, system prompt, AAD app values).
  • A future offer version ships a template change — for template-level changes we contact you first; nothing re-deploys behind your back.

What never updates automatically

  • The Teams app in your tenant. If a new runtime version changes the Teams manifest, re-download the .zip from Teams setup and re-upload it in Teams Admin Center — the stable manifest id makes it an in-place upgrade (details).
  • The widget script tag on your website. The tag itself never needs changing; the bundle behind /api/widget.js updates with the runtime.