Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from repo
Assess and migrate workloads from AWS, GCP, or other clouds to Azure services.
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
references/services/app-service/assessment.md
1# Assessment Phase23Generate a migration assessment report before any code changes.45## Prerequisites67- Workspace contains source platform project files (Procfile, app.yaml, .ebextensions, etc.)8- Prompt user to upload relevant files if not present910## Assessment Steps11121. **Identify Application** — Determine app type (web, API, worker), runtime, and framework132. **Map Platform Services** — Map source services to Azure equivalents (see scenario-specific references)143. **Map Properties** — Map compute config (instance size, scaling) to App Service Plan properties154. **Check Dependencies** — List 3rd-party libraries and verify Azure compatibility165. **Analyze Code** — Check for platform-specific APIs, SDKs, or patterns that need migration176. **Map Data Services** — Identify database and storage migration paths187. **Map Deployment** — Identify equivalent Azure deployment strategies (azd, GitHub Actions, Bicep)198. **Review CI/CD** — Check pipeline compatibility with Azure DevOps or GitHub Actions209. **Map Monitoring** — Map observability stack → Application Insights / Azure Monitor2122## Code Preview2324During assessment, show a **sneak peek** of key configuration changes:25- Startup command / Dockerfile adjustments26- App Settings mapping27- Database connection string migration (to managed identity)2829This helps the user understand the migration scope before committing.3031## Architecture Diagrams3233Generate two diagrams:341. **Current State** — Source platform architecture with services and integrations352. **Target State** — Azure architecture showing equivalent App Service structure3637## Assessment Report Format3839> ⚠️ **MANDATORY**: Use these exact section headings in every assessment report. Do NOT rename, reorder, or omit sections.4041The report MUST be saved as `migration-assessment-report.md` inside the output directory (`<source-folder>-azure/`).4243```markdown44# Migration Assessment Report4546## 1. Executive Summary4748| Property | Value |49|----------|-------|50| **Application Name** | <name> |51| **Application Type** | Web App / API / Worker |52| **Source Platform** | <Heroku / Elastic Beanstalk / App Engine> |53| **Source Runtime** | <runtime and version> |54| **Target Platform** | Azure App Service |55| **Target Runtime** | <runtime and version> |56| **Migration Readiness** | <High / Medium / Low> |57| **Estimated Effort** | <Low / Medium / High> |58| **Assessment Date** | <date> |5960## 2. Application Inventory6162| # | Component | Runtime | Type | Instances | Description |63|---|-----------|---------|------|-----------|-------------|64| 1 | | | Web / Worker / Cron | | |6566## 3. Service Mapping6768| Source Service | Azure Equivalent | Migration Complexity | Notes |69|----------------|------------------|----------------------|-------|70| | | | |7172## 4. Compute & Scaling Mapping7374| # | Source Config | Value | Azure Equivalent | Azure Value | Notes |75|---|-------------|-------|------------------|-------------|-------|76| 1 | Instance type | | App Service Plan SKU | | |77| 2 | Auto-scaling | | App Service Autoscale | | |78| 3 | Health check | | Health Check feature | | |7980## 5. Dependencies Analysis8182| # | Package/Library | Version | Platform-Specific? | Azure Equivalent | Compatible? | Notes |83|---|----------------|---------|---------------------|------------------|-------------|-------|84| 1 | | | | | | |8586## 6. Environment Variables & Configuration8788| # | Source Variable | Purpose | Azure Equivalent | Auth Method | Notes |89|---|---------------|---------|------------------|-------------|-------|90| 1 | | | App Setting / Key Vault | Managed Identity / App Setting | |9192## 7. Architecture Diagrams9394### 7a. Current State (Source Platform)9596<!-- Mermaid or ASCII diagram -->9798### 7b. Target State (Azure)99100<!-- Mermaid or ASCII diagram -->101102## 8. Data Services Mapping103104| Source Database/Storage | Azure Equivalent | Migration Path | Notes |105|------------------------|------------------|----------------|-------|106| | | | |107108## 9. Networking & Security Mapping109110| Source Feature | Azure Equivalent | Notes |111|---------------|------------------|-------|112| Custom domain | App Service Custom Domain | |113| SSL/TLS | App Service Managed Certificate / BYO cert | |114| VPN/VPC | VNet Integration | |115116## 10. Monitoring & Observability Mapping117118| Source Service | Azure Equivalent | Migration Notes |119|---------------|------------------|-----------------|120| | Application Insights | |121| | Azure Monitor Metrics | |122| | Azure Monitor Alerts | |123124## 11. CI/CD & Deployment Mapping125126| Source Tool | Azure Equivalent | Notes |127|------------|------------------|-------|128| | GitHub Actions / Azure DevOps | |129| | Bicep / ARM Templates | |130| | Deployment Slots | |131132## 12. Recommendations1331341. **Runtime**: <recommended App Service runtime stack and version>1352. **App Service Plan**: <Free / Basic / Standard / Premium v3>1363. **IaC Strategy**: <Bicep with azd / Terraform>1374. **Auth Strategy**: <Managed Identity for all service-to-service>1385. **Monitoring**: <Application Insights + Azure Monitor>139140## 13. Next Steps141142- [ ] Review and approve this assessment report143- [ ] Proceed to code migration (azure-cloud-migrate Phase 2)144- [ ] Hand off to azure-prepare for IaC generation145```146147> 💡 **Tip:** Use `mcp_azure_mcp_get_azure_bestpractices` tool to learn App Service best practices for the comparison.148