full-day workshop: Align Azure deployment steps with current azd infrastructure generation

Problem

Exercise 8 runs azd init --from-code and immediately tells learners to edit infra/resources.bicep. That file is not tracked in the template. The checked-in next-steps.md, generated for the current azd flow, states that azd initially generates infrastructure in memory and that learners must run azd infra gen to persist infra/main.bicep, infra/resources.bicep, and modules.

The exercise therefore assumes a generated file that may not exist. It also relies on a fixed location near line 130 and specific client/server output names, although generated azd output can vary by version and detection result.

Suggested change

Pin or state a tested azd version and document the complete, reproducible path that creates editable Bicep before asking learners to modify it.

Acceptance criteria

• A fresh run produces infra/resources.bicep before the edit step, with any required azd infra gen command documented.
• The supported/tested azd version is stated.
• Learners validate the services detected by azd init --from-code.
• The API_SERVER_URL edit identifies the correct resource structurally rather than by approximate line number.
• Bicep validation runs before azd pipeline config.
• The generated workflow and deployed endpoints are verified using the documented flow.

Start with Exercise 8 and the checked-in next-steps.md, then run azd init --from-code and azd infra gen to compare the generated infra/main.bicep, infra/resources.bicep, and modules with the documented flow. Document a tested azd version, service validation, structural API_SERVER_URL guidance, Bicep validation, and verification of the generated workflow and deployed endpoints.