Each old app keeps its passwords and keys (storage, Amazon, Shopify…) in Azure. Optimus Nine needs the same ones. This tool does the renaming for you — nothing you paste leaves this browser.

1. In the Azure portal open Optimus Nine (your Static Web App) → Settings → Environment variables → Advanced edit. Select everything in that box, copy, and paste it into the first box below.
2. Do the same for each old app — Sales Console, pg-planner, Atom Ads, Glean (each is its own Static Web App in the Azure portal) — pasting each into its own box.
3. Click Build the new list, then Copy.
4. Back in Optimus Nine's Advanced edit: select everything, paste over it, click OK, then Apply at the bottom of the page. Come back here and click Re-check.

No “Advanced edit” button? Use Cloud Shell instead — the >_ icon at the top of the Azure portal (choose Bash; if it asks about storage, choose No storage account required). To read an app's settings, type az staticwebapp appsettings list -n NAME (NAME = the app's name in the Static Web Apps list) and paste what it prints into that app's box. After Build the new list, use Copy Cloud Shell command and paste it into Cloud Shell — it saves the list to Optimus Nine.

The Sales Console saves straight from your browser into Azure storage, and storage only accepts saves from addresses on its allowed list. Add Optimus Nine's address to that list:

1. Azure portal → the storage account the Sales Console uses (the one named in its storage connection) → left menu Settings → Resource sharing (CORS) → Blob service tab.
2. There's already a row for the old Console address. Add a new row just like it, but with Allowed origins set to (same methods, headers and max age). Click Save.
3. To check: open Sales Console from the left rail — your data should load, and saving should work.

Click Test now after step 1. Each app should say ● WORKING. If one doesn't, the message says which setting to fix.

Anything outside Optimus Nine that calls an old app (Make.com scenarios, data connectors) must use the new address. Only the start of the address changes — keys, headers and body stay exactly the same:

https://<old app>.azurestaticapps.net/api/…  →  /api/<module>/…   where module is console, mrp, atom or glean.

The ones we know about — open each in Make.com or your connector settings, swap the address, save:

When an app sends you to Amazon or Microsoft to connect an account, they send you back to an address saved on their side. Existing connections keep working without this — you only need it to reconnect Amazon Ads, or to send PO emails from pg-planner / use Glean's SharePoint & email buttons.

1. Amazon Ads (Atom → Connect Amazon): Amazon developer console → Login with Amazon → your security profile → Web Settings → Allowed Return URLs → add
2. Microsoft (pg-planner PO emails, Glean SharePoint/email): Microsoft Entra admin center → App registrations → the app whose ID is in pg-planner's / Glean's settings → Authentication → Single-page application → Add URI: and a second one with a slash on the end, / (pg-planner uses the first, Glean the second). Save.

Once every app opens from Optimus Nine with your data, delete or stop the four old Static Web Apps. Don't delete their storage accounts — Optimus Nine uses them. This matters: the old sites let anyone with any Microsoft account sign in and read your data; Optimus Nine only lets in people on your access list.