AGENTIC MEMORY

Skills

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

← Back to Skills

azure-validate

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.

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-validate 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 · 17

references/aspire-functions-secrets.md

Aspire + Azure Functions: Secret Storage Validation

⚠️ Pre-provisioning check — Run this BEFORE azd provision.

When This Applies

This check is required when all of these are true:

| Condition | How to detect | |-----------|--------------| | .NET Aspire project | *.AppHost.csproj exists or Aspire.Hosting package reference | | Azure Functions component | AddAzureFunctionsProject call in AppHost.cs or Program.cs | | Identity-based storage | WithHostStorage call (Aspire default) |

Detection

Run the scan script — it finds *.cs files that call AddAzureFunctionsProject, checks whether each one already sets AzureWebJobsSecretStorageType, and prints a single verdict so you don't have to parse raw grep output.

Bash — scripts/scan-aspire-functions-secrets.sh:

./scripts/scan-aspire-functions-secrets.sh [directory]   # directory defaults to .

PowerShell — scripts/scan-aspire-functions-secrets.ps1:

.\scripts\scan-aspire-functions-secrets.ps1 [-Path <directory>]   # -Path defaults to .

The script prints one of three verdicts:

| Verdict | Meaning | Action | |---------|---------|--------| | NOT APPLICABLE | No AddAzureFunctionsProject call found | Skip this check | | ALREADY CONFIGURED | Every matching file already sets AzureWebJobsSecretStorageType | No change required | | FIX REQUIRED | Matching file(s) call AddAzureFunctionsProject but omit the setting (file/line listed) | Apply the Fix below to each listed file |

Fix

Add .WithEnvironment("AzureWebJobsSecretStorageType", "Files") to the Azure Functions project builder chain in the AppHost source file that contains the AddAzureFunctionsProject call (often Program.cs in the *.AppHost project).

Before

var functions = builder.AddAzureFunctionsProject<Projects.MyFunctions>("functions")
    .WithHostStorage(storage)
    .WithReference(queues);

After

var functions = builder.AddAzureFunctionsProject<Projects.MyFunctions>("functions")
    .WithHostStorage(storage)
    .WithEnvironment("AzureWebJobsSecretStorageType", "Files")
    .WithReference(queues);

💡 Tip: Place .WithEnvironment(...) immediately after .WithHostStorage(...) for clarity.

Why This Is Required

Azure Functions needs storage for managing host secrets/keys (function keys, host keys, master key). By default, it stores them as blobs in the AzureWebJobsStorage account.

When Aspire configures identity-based storage access (via WithHostStorage), it sets URI-based environment variables like AzureWebJobsStorage__blobServiceUri instead of a connection string. The Functions runtime's secret manager does not support these identity-based URIs — it requires either a connection string or SAS token.

Setting AzureWebJobsSecretStorageType=Files switches the Functions host to file-system-based key storage, bypassing the blob storage dependency for secrets.

Error Without This Setting

System.InvalidOperationException: Secret initialization from Blob storage failed
due to missing both an Azure Storage connection string and a SAS connection URI.
For Blob Storage, please provide at least one of these.

When This Check Does NOT Apply

| Scenario | Why | |----------|-----| | Aspire project without Azure Functions | No Functions secret manager involved | | Standalone Azure Functions (not Aspire) | Uses connection string by default | | Functions with explicit connection string | AzureWebJobsStorage is a full connection string, not identity-based | | AzureWebJobsSecretStorageType already set | Configuration is already present |