Set up Azure Deployment Preflight and review safely

This guide presents a controlled way to start with Azure Deployment Preflight. The skill supplies instructions for an assistant; the team remains responsible for the identity, target, and execution.

Source and setup

Open the official source path in the github/awesome-copilot repository and review the current SKILL file before adopting it in your preferred Copilot or coding agent. Follow only the integration method documented for that client. Do not copy unknown files from search results, and never place tokens in configuration files.

Prepare the project

Decide which Bicep templates and parameter files are in scope. Check whether azure.yaml exists, identify the template target scope, and confirm which environment is intended. Verify the active identity and subscription through established team procedures. Do not provide secret values to the assistant; use an existing local sign-in or an approved secure reference instead.

Run the review

Ask the assistant for an inventory first and then for Bicep syntax validation. Request a what-if preview using the correct Azure deployment scope. Review every proposed change individually. Pay special attention to deletions, access-control changes, network rules, identities, databases, and production resources. If Provider validation is unavailable because of RBAC, record the reduced confidence and the reason in the report.

Report and approval

Keep a report containing the files reviewed, target scope, tool versions, errors, warnings, and recommendations. Remove credentials, tokens, personal data, and unnecessary parameter values from the report. A what-if preview is not an approval. A responsible reviewer confirms the subscription, change set, and rollback plan before a separate deployment step is executed.

FAQ

Question: Can the skill approve a deployment by itself? Answer: No. It organizes checks and previews. Technical and business approval remains with responsible people.

Question: What if Azure CLI or Bicep CLI is unavailable? Answer: Record the missing tool step as a limitation. Install tools only after internal approval and use trusted distribution sources.

Question: May I paste a real token into a prompt? Answer: No. Tokens and other secrets belong in neither prompts nor reports nor version control.