AGENTIC MEMORY

Skills

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

← Back to Skills

azure-upgrade

Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, change hosting plan, function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs (com.microsoft.azure to com.azure), migrate Azure Cache for Redis (ACR/ACRE) to Azure Managed Redis (AMR).

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-upgrade 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 · 49

references/services/functions/consumption-to-flex/windows/workflow.md · 24000

Consumption | |----------|-------------|------------------| | SKU | Y1 (Dynamic) | FC1 (FlexConsumption) | | Plan required | Optional (auto-created) | Required (must be explicit) | | OS | Windows | Linux | | Configuration | App settings | functionAppConfig section | | Storage | WEBSITE_CONTENTSHARE setting | deployment.storage in functionAppConfig |

If the source app is managed through Bicep, ARM, or Terraform:

  1. Define the Flex app and plan as new resources; a Consumption app cannot be converted to Flex Consumption in place.
  2. Update the deployment definitions to use the new resource names and the Flex configuration above.
  3. Reconcile resources created during migration instead of allowing IaC to recreate or overwrite them. For Terraform, import the new resources when appropriate.
  4. Review the proposed changes with az deployment group what-if or terraform plan before applying them.
  5. Update CI/CD pipelines to deploy to the new Flex app.

Do not mix ongoing manual configuration with resource-based deployments. If the app is not managed through IaC, skip this section.

Deprecated Settings (Do NOT Migrate)

These app settings must be filtered out before applying to the new Flex app (Step 4c). The skill handles this automatically — Step 4c streams source settings through jq, deleting these keys in memory before PATCHing the new app's ARM endpoint.

Azure Files content settings (always present on Windows Consumption — never migrate)

Every Windows Consumption app has these because the platform requires them for the Azure Files SMB share. Flex uses blob-based deployment instead — these have no equivalent.

These platform content settings are distinct from explicit Azure Files mount metadata returned by az webapp config storage-account list. Windows Consumption doesn't support explicit storage mounts, so catalog any returned metadata but don't migrate it.

  • WEBSITE_CONTENTAZUREFILECONNECTIONSTRING
  • WEBSITE_CONTENTSHARE
  • WEBSITE_CONTENTOVERVNET
  • WEBSITE_SKIP_CONTENTSHARE_VALIDATION

Deployment settings (Flex uses deployment.storage in functionAppConfig, not app settings)

Windows Consumption has three historical aliases for run-from-package — all must be removed:

  • WEBSITE_RUN_FROM_PACKAGE
  • WEBSITE_RUN_FROM_ZIP (legacy alias — same semantics as WEBSITE_RUN_FROM_PACKAGE)
  • WEBSITE_USE_ZIP (original name — same semantics)

Runtime / scale settings (configured via functionAppConfig in Flex, not app settings)

  • FUNCTIONS_EXTENSION_VERSION
  • FUNCTIONS_WORKER_RUNTIME
  • FUNCTIONS_WORKER_RUNTIME_VERSION
  • FUNCTIONS_MAX_HTTP_CONCURRENCY
  • FUNCTIONS_WORKER_PROCESS_COUNT
  • FUNCTIONS_WORKER_DYNAMIC_CONCURRENCY_ENABLED
  • WEBSITE_MAX_DYNAMIC_APPLICATION_SCALE_OUT

Other unsupported settings

  • WEBSITE_USE_PLACEHOLDER_DOTNETISOLATED
  • WEBSITE_LOAD_CERTIFICATES (unused in Flex; use the site-scoped certificate process and make certificates accessible to app code)
  • AzureWebJobsDashboard (legacy v1 setting — not used by the v4 runtime)
  • WEBSITE_MOUNT_ENABLED
  • ENABLE_ORYX_BUILD
  • SCM_DO_BUILD_DURING_DEPLOYMENT
  • WEBSITE_DNS_SERVER
  • WEBSITE_NODE_DEFAULT_VERSION
  • WEBSITE_VNET_ROUTE_ALL

Application Insights (preserved from Step 4b and verified by Step 4k)

  • APPLICATIONINSIGHTS_CONNECTION_STRING — Step 4c preserves the target-specific value normally created by az functionapp create; Step 4k verifies it without displaying the value. APPLICATIONINSIGHTS_AUTHENTICATION_STRING=Authorization=AAD is preserved only when the source already used AAD ingestion.

Storage (replaced by Step 4b / 4b.opt)

Every setting whose name starts with AzureWebJobsStorage is dropped by the 4c filter. Preserve the target binding verified by Step 4b or configured by Step 4b.opt:

  • AzureWebJobsStorage — discard the source connection string. Step 4b creates a fresh target connection string only when Shared Key authentication is permitted; identity-first targets must not receive one.
  • All AzureWebJobsStorage__* variants — discard source settings so they can't silently point the target runtime at the wrong account. Preserve verified target identity settings or re-derive them through 4b.opt where conversion is permitted.