README & usability fit and finish#17
Merged
Merged
Conversation
The script printed 'Run func start to start the host', which is incomplete and skips the actual local-run workflow documented in the README: azurite --silent --skipApiVersionCheck --location .azurite # terminal A uv run func start # terminal B uv run python chat.py # terminal C Updated both the bash and PowerShell variants to print the three-terminal block so users land on the working path without re-reading the README. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Customize-before-teardown reads more naturally. Promotes 'Make it yours' into step 6 of the Quickstart, with 'Clean up' as the closing step 7. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sets MAILBOX_OWNER_EMAIL (required for LIVE mail) and the optional TEAMS_TEAM_ID / TEAMS_CHANNEL_ID before `azd up`, so the deployed agents are LIVE on first deploy instead of starting in DRY RUN with placeholder values. Renumbers the trailing Quickstart steps. Stacks on top of #13 (Make it yours before Clean up). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Chain hydrate-local-settings before configure-trigger so 'azd up' / 'azd provision' keeps both the deployed Function App app settings AND local.settings.json in sync from the same source of truth (azd env). Today, 'azd env set MAILBOX_OWNER_EMAIL ...' followed by 'azd provision' pushes the new value to the deployed app but leaves local.settings.json stale — the local chat client then reports 'Partial: placeholder' even though the deployed app is correctly LIVE. Stacks on #15. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The 'Show config readiness' doctor only inspected env vars; if the local
Functions host wasn't running, you'd only learn that when an agent call
failed with a generic 'Connection refused'. And there was no documented
way to point chat.py at the deployed cloud Function App.
This adds:
* `infra/scripts/use-cloud-host.{sh,ps1}` — sourceable helpers that
export AGENT_URL + FUNCTION_KEY from `azd env` + `az functionapp
keys list`, so the chat client hits the deployed Function App in
Azure without running azurite + func start locally.
* Doctor (option 4) shows a new 'Functions host' row up top with
🟢/🔴 + which host (local vs cloud) is being targeted and whether
it's reachable.
* When a chat call fails with a connection error, the hint now spells
out BOTH paths: the 3-terminal local setup AND the one-liner to
switch to the deployed cloud host.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
Author
|
Added 5th commit: Tested live in a deployed env: doctor flips local 🔴 → cloud 🟢 after |
Daily Briefing is the most concrete, demo-able value of the agent — it's what people see on day one once they've deployed. Lead with it and use the full noun phrase 'Daily Briefing' (matches the menu label in chat.py and the agent name) instead of the verb-form 'Brief'. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
nzthiago
approved these changes
Jun 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Four small, related fit-and-finish fixes to the README + first-run UX. Each commit stands alone; bundling here per author preference.
hydrate-local-settingsnext-step hintinfra/scripts/hydrate-local-settings.{sh,ps1}Run 'func start', but the README's local-run workflow needs three terminals (azurite, func start, chat client). Replaces the one-liner with the real three-terminal hint so the script output matches the docs.README.mdREADME.mdMAILBOX_OWNER_EMAIL+ Teams ids beforeazd up, so the very first deploy is LIVE instead of placeholder DRY-RUN.azure.yaml: hydratelocal.settings.jsonin postdeployazure.yamlazd env set X+azd provisionpushes new values to the deployed Function App but silently leaveslocal.settings.jsonstale, so the chat client falsely reports 🟡 Partial even though the deployed app is LIVE. Chaining hydrate into postdeploy keeps both in sync from one source of truth (azd env).Final Quickstart numbering after this PR
##after QuickstartRepro of the split-brain bug fixed by commit 4
azd up(placeholders inazd env).azd env set MAILBOX_OWNER_EMAIL me@tenant.comazd provision— deployed Function App now LIVE (verified viaaz functionapp config appsettings list).uv run python chat.py— doctor reports 🟡 Partial: MAILBOX_OWNER_EMAIL is a placeholder.Because step 3 leaves
local.settings.jsonstale and the chat client reads from there.With commit 4, step 3's postdeploy rehydrates
local.settings.jsonautomatically and the chat client correctly shows �� LIVE on next launch.Risk
azure.yamlchange just chains two existing scripts in a single hook — if hydrate fails,&&(or the powershellif ($LASTEXITCODE...)) stops the chain, same behavior as today.Out of scope (filed separately)
#14— postdeploy hook can race the function-host cold start for theconnector_extensionsystem key (separate bug, separate fix).Tested
Locally end-to-end on
~/src/m365-test1withazd up,azd env set,azd provision,uv run python chat.py. Doctor flips 🟡 → 🟢 with no manual hydrate.Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com