AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-prepare

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-prepare at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 164

references/functional-verification.md

Functional Verification

Verify that the application works correctly — both UI and backend — before proceeding to validation and deployment. This step prevents deploying broken or incomplete functionality to Azure.

When to Verify

After generating all artifacts (code, infrastructure, configuration) and applying security hardening — but before marking the plan as Ready for Validation.

Verification Checklist

Use ask_user to confirm functional testing with the user:

"Before we proceed to deploy, would you like to verify the app works as expected?
We can test both the UI and backend to catch issues before they reach Azure."

Backend Verification

| Check | How | |-------|-----| | App starts without errors | Run the app and confirm no startup crashes or missing dependencies | | API endpoints respond | Test core routes (e.g., curl health, list, create endpoints) | | Data operations work | Verify CRUD operations against storage, database, or other services | | Authentication flows | Confirm auth works (tokens, managed identity fallback, login/logout) | | Error handling | Verify error responses are meaningful (not unhandled exceptions) |

UI Verification

| Check | How | |-------|-----| | Page loads | Open the app in a browser and confirm the UI renders | | Interactive elements work | Test buttons, forms, file inputs, navigation links | | Data displays correctly | Verify lists, images, and dynamic content render from the backend | | User workflows complete | Walk through the core user journey end-to-end (e.g., upload → view → delete) |

Decision Tree

App artifacts generated?
├── Yes → Ask user: "Would you like to verify functionality?"
│   ├── User says yes
│   │   ├── App can run locally? → Run locally, verify backend + UI
│   │   ├── API-only / no UI? → Test endpoints with curl or similar
│   │   └── Static site? → Open in browser, verify rendering
│   │   Then:
│   │   ├── Works → Proceed to Update Plan (step 6)
│   │   └── Issues found → Fix issues, re-test
│   └── User says no / skip → Proceed to Update Plan (step 6)
└── No → Go back to Generate Artifacts (step 3)

Running Locally

For apps that can run locally, help the user start the app based on the detected runtime:

| Runtime | Command | Notes | |---------|---------|-------| | Node.js | npm install && npm start | Set PORT=3000 if not configured | | Python | pip install -r requirements.txt && python app.py | Use virtual environment | | .NET | dotnet run | Check launchSettings.json for port | | Java | mvn spring-boot:run or gradle bootRun | Check application.properties |

⚠️ Warning: For apps using Azure services (e.g., Blob Storage, Cosmos DB), local testing requires the user to be authenticated via az login with sufficient RBAC roles, or to have local emulators configured (e.g., Azurite for Storage).

Record in Plan

After functional verification, add a note to .azure/deployment-plan.md:

## Functional Verification
- Status: Verified / Skipped
- Backend: Tested / Not applicable
- UI: Tested / Not applicable
- Notes: <any issues found and resolved>