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/recipes/azd/environment.md

AZD Environment Setup

⛔ MANDATORY: You MUST set up an AZD environment before running any deployment commands.

Step 1: Check Existing Environments

azd env list

If an environment is already selected (marked with *), check its current values:

azd env get-values

If AZURE_ENV_NAME, AZURE_SUBSCRIPTION_ID, and AZURE_LOCATION are already set, confirm with user:

Question: "An AZD environment is already configured. Would you like to use it?"

  Environment: {env-name}
  Subscription: {subscription-id}
  Location: {location}

Choices: [
  "Yes, use this environment (Recommended)",
  "No, create a new environment"
]

If user confirms → skip to Verify Configuration. Otherwise → continue to Step 2.

If NO environment exists or none is selected:

  • Continue to Step 2

Step 2: Create New Environment

⛔ DO NOT use generic names like "dev", "prod", or "test"

These cause naming conflicts in Azure resource groups and resources. Always generate a unique name.

Generate Suggested Name

Use this pattern:

{project-name}-{random-4-chars}

Examples:

  • dadjokes-x7k2
  • todoapp-m3p9
  • myapi-q5w8

Prompt User

You MUST use ask_user to confirm the environment name:

I need to create an AZD environment for this deployment.

Suggested name: {project-name}-{random-4-chars}

Would you like to use this name or enter a custom one?

Create Environment

After user confirms:

azd env new <environment-name> --no-prompt

Step 3: Configure Environment

Set subscription and location:

azd env set AZURE_SUBSCRIPTION_ID <subscription-id>
azd env set AZURE_LOCATION <location>

Verify Configuration

azd env get-values

Confirm these values are set:

  • AZURE_ENV_NAME
  • AZURE_SUBSCRIPTION_ID
  • AZURE_LOCATION

Only Then Proceed

After environment is configured, proceed with azd up --no-prompt.