Skip to content

Upgrade to Build 1852

Sam Betts edited this page Nov 4, 2026 · 5 revisions

Updating the solution → Upgrade to Build 1852

This page is for administrators whose deployment is on Stable 1850 or older. Stable 1852 added three migrations and several optional services, so read this page before you upgrade to 1852 or any later build. It lists what changes, the exact order of the three manual scripts, how long they take, and the checks specific to 1852. You don't have to install 1852 itself: a later build's installer applies these migrations too. For the general method, and for skipping several releases in one upgrade, see Updating the solution.

Stable build 1852 (upgrading from 1850)

Published 14 October 2026. Stable build 1852 contains these Framework changes, merged into code main at f539794c. Use the matching 1852 binaries and schema assets; do not substitute later dev or local changes.

Upgrade question What changes from 1850
Runtime Still Windows / .NET Framework 4.8. SDK-style project maintenance is not a .NET 10 migration
SQL Three purely additive migrations below; existing tables/indexes are not rebuilt or backfilled by these migrations
Saved installer JSON 3.0.0 → 3.1.0 adds the Agent 365 import toggle; 3.1.0 → 3.2.0 adds optional Foundry fields; 3.2.0 → 3.3.0 adds Azure OpenAI deployment type (older configs retain regional Standard). Old files load; re-saving with 1852 stamps 3.3.0
Defaults Agent 365 catalog import and Foundry provisioning are off. Provisioning a model does not enable prompt processing: a separate durable administrator opt-in is required
Permissions Administration and See PII stay independent. Bypassing a global report filter now needs both; Administration alone no longer bypasses it
Optional services Agent 365 needs its licence and CopilotPackages.Read.All; prompt categories need history consent, model access and durable opt-in; billing consumption needs a connected administrator
Downtime Plan a quiet window. Standard upgrades stop the site around schema work; the standalone website-deployment script also uses ARM stop/start. Additive DDL is brief but a schema lock can wait on readers/writers

Exact migration and manual-script order

Start from a database stamped through 202610021200001_LicenceHistory. If older migrations are still pending, run their scripts first, in order: see the full script chain.

  1. 202610071200001_Agent365PackageCatalog — new empty catalog/import/element tables and their own indexes.
  2. 202610071400001_CopilotTurnPairing — nullable copilot_chats.conversation_id (no default; metadata-only) plus the empty copilot_chat_duplicates table and its own indexes.
  3. 202610080900001_AddPromptCategories — empty immutable taxonomy/classification tables.

For a DBA upgrade, use each exact matching <migration-id>.manual.sql file, in this order. Each validates/stamps with its immediate predecessor, copies the same EF model snapshot, and safely applies/stamps or no-ops on rerun. Do not edit __MigrationHistory by hand or skip a predecessor.

Release downloads are available. Stable 1852 includes all three matching .manual.sql assets and all five component ZIPs. Use those assets together; a later testing build's files are not substitutes.

Create DB.sql is unchanged: these objects are migration-owned, not additions to that legacy bootstrap file. Do not recreate the database or rerun a create script over an existing installation.

The release-review fixes to settings timeouts, report availability, billing outcomes, catalog dates and counted-turn governance use the updated binaries/SQL extensions. They add no fourth migration or app setting: the chain above and installer schema 3.3.0 are the 1852 target. Stored echo DLP copies are repaired only when affected turns are revisited by import batches, not by a whole-history migration; see turn counting and bounded repair.

Additive DDL timing, not whole-upgrade timing

Planning estimates for an otherwise healthy, quiet database, excluding lock waits, downloads, deployment and any separate data repair:

Migration 1M existing fact rows 10M existing fact rows 100M existing fact rows
Agent 365 catalog About 1–5 seconds About 1–5 seconds About 1–5 seconds
Copilot turn pairing About 1–5 seconds About 1–5 seconds About 1–5 seconds
Prompt categories About 1–5 seconds About 1–5 seconds About 1–5 seconds

These are size-independent metadata/empty-table estimates, not measured production promises. There is no existing-table index build, backfill or rewrite in these three migrations. The nullable column needs a brief schema-modification lock; a long transaction can make that wait much longer than the DDL itself. Pause importers and report refreshes rather than assuming the lock cannot block. Older pending migrations and upgrade SQL repairs have their own costs.

Upgrade checklist

Follow the general steps in Upgrade with the installer, or the manual (DBA) path. For 1852, also:

  1. Plan for the website restart. Pause both continuous WebJobs and scheduled reporting/profiling activity for a quiet window, and account for App Service stop/start. If you deploy the website content with Deploy-AppServiceContent.ps1 rather than the installer, supply its resource-group/subscription target and ARM read/stop/start rights—a publish profile alone is insufficient.
  2. Keep the new services off until they are ready. When you re-save the configuration (the 1852 installer saves schema 3.3.0; a later installer saves its own, later schema), review the defaults and the optional Azure AI provisioning. Keep Agent 365, prompt categories and the billing connection off unless their governance, licences, consent and cost/quota requirements are ready. Provisioning a model does not enable prompt processing.
  3. Apply the schema before the new importers run. Use the installer's schema upgrade, or the three manual scripts above. The standard schema upgrade also refreshes the reporting/maintenance SQL extensions that 1852's fixes use; manual migration scripts alone do not replace that step, so after them run Forcing schema updates.
  4. If deployment fails part-way, for example during ZIP extraction, keep the maintenance window open and rerun the same target build after fixing the cause; a partial extraction is not success.
  5. After deploying, sign in to the portal and check that people with Administration and See PII still have the access they need: bypassing a report filter now needs both roles. Expect an informational billing connection required state until a delegated administrator is connected. It is not evidence of zero consumption.
  6. Compare figures with care. Keep any baseline workbooks you need before upgrading. Check known upgrade effects: paired-turn counts and maker-testing exclusions can lower agent figures without adoption falling. Old credit estimates and discarded prompt text are not retroactively rebuilt.

Return to Updating the solution · All topics in this guide

Previous: Upgrade to Build 1856 · Next: Upgrade from Redis

Start here

Copilot analytics

Using the portal

Install & configure

Beyond Copilot

Operate

Upgrading from an older build

Reference

Project

Clone this wiki locally