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/automation/access-key-copy.md

Access Key Copy

5a. Apply the Access Key Strategy

Run only after Step 5 verifies that all target functions synchronized. If Step 4l selected target-generated keys, mark this step skipped - target-generated keys selected and record that key-dependent clients must be updated before HTTP cutover.

If preservation was selected, process only HTTP-triggered functions from the verified Step 4j trigger inventory. Match those source and target functions by exact name. For a keyed source HTTP function without an exact target match, ask whether it was removed or renamed. Skip removed functions with a recorded reason; require an explicit source-to-target name mapping for renamed functions.

Fetch key values only into process memory. For each source host key, run:

az functionapp keys set --name <NEW_APP_NAME> --resource-group <RESOURCE_GROUP> --key-type functionKeys --key-name <KEY_NAME> --key-value <KEY_VALUE> --output none --only-show-errors

For each key returned by az functionapp function keys list for each mapped HTTP function, run:

az functionapp function keys set --name <NEW_APP_NAME> --resource-group <RESOURCE_GROUP> --function-name <TARGET_FUNCTION_NAME> --key-name <KEY_NAME> --key-value <KEY_VALUE> --output none --only-show-errors

Use jq in Bash and ConvertFrom-Json in PowerShell to enumerate the in-memory functionKeys object and per-function key properties. Exclude the per-function metadata fields id, kind, name, properties, and type. Check $LASTEXITCODE after every native command in PowerShell. Clear every JSON object, key value, and derived row in trap/finally.

⚠️ --key-value briefly exposes the value in the Azure CLI child process arguments. Run only in a trusted terminal, never enable shell tracing or CLI debug output, and use --output none --only-show-errors. Never write keys to migration artifacts or temporary files.

Reruns are idempotent: setting the same name and value overwrites the matching target key. Preserve target-only keys; don't delete anything.

After all writes, re-list source and target host keys and HTTP-function keys into memory and compare every selected name and value. Report only counts and pass/fail results. On any mismatch or CLI failure, clear variables, mark Step 5a blocked, and don't begin HTTP validation or cutover.

List target system-key names after deployment and record which webhook integrations need their target-generated values. Never copy or display the _master key or system-key values.