… 6 unchanged lines …
  
  ## Key facts
  
+ - **Microsoft is steering people off it (September 2026).** The overview page now carries an IMPORTANT note saying app building is available in [Copilot Cowork](https://learn.microsoft.com/en-us/microsoft-365/copilot/cowork/use-cowork) and will roll out to Copilot Studio soon, and that those are the recommended experiences going forward. Vibe hasn't been retired, but it is no longer the direction of travel.
  - Reached through `vibe.powerapps.com`, or from the maker portal via **Try new experience (Preview)** — which you have to re-enable at every sign-in if you go that route.
  - A tenant admin must switch on **Copilot in Power Apps (preview)** in Power Platform admin centre tenant settings first.
  - **Not available in the default environment.** At preview it runs only in US, Australia, Asia and India regions, and only in English.
    … 20 unchanged lines …
  
  ## Gotchas
  
+ - Don't start a client on vibe now without saying out loud that Microsoft has pointed at Copilot Cowork and Copilot Studio instead. A preview the vendor has already recommended moving away from is a different risk conversation from a preview that's simply early.
  - The disconnection at conversion is the one that hurts. Teams convert early, keep iterating in vibe because it's faster, then discover the two apps have diverged with no merge path.
  - `power.config.json` has to be salvaged by hand — copy `connectionReferences` and `databaseReferences` out, delete the file, run `pa app init`, paste them back into the new one. Miss it and the converted app has no data.
  - Missing images after conversion look like a broken build. They're a CSP problem, and nothing in the error output says so.
    … 2 unchanged lines …
  
  ## Consultant notes
  
+ - The September 2026 pointer to Copilot Cowork changes the recommendation. If a client is choosing today rather than already mid-flight, look at the Cowork app skill first and treat vibe as the fallback for what Cowork can't do yet — not the default.
  - Sell it as an accelerator for the requirements phase, never as a build tool. The demo is spectacular and clients will hear "we don't need developers"; the conversion path proves the opposite, so show that in the same session.
  - The region restriction is the first question to ask, before anyone gets excited. A UK or EU tenant with no US/APAC environment cannot use this today, and finding that out after a scoping workshop is an avoidable embarrassment.
  - Post-go-live risk sits entirely in the one-way conversion. Anything that reaches production must be the code app, with the vibe app formally retired — otherwise you end up supporting a shadow copy that a business user keeps editing.
    … 1 unchanged line …
  
  ---
  
- *Preview feature — worth revisiting when region and language coverage widen and if a two-way sync to code apps appears.*
+ *Preview feature Microsoft is already pointing away from — revisit when app building lands in Copilot Studio, or if vibe gets a retirement date.*