azure-configurator

Configure and verify Azure resources including Key Vault secrets, RBAC assignments, PostgreSQL and storage containers after IaC deployment.

9|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/TykoDev/SupremeTeam --skill azure-configurator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-configurator
Source: https://github.com/TykoDev/SupremeTeam/tree/main/skills/azure/azure-configurator
Command: npx skills add https://github.com/TykoDev/SupremeTeam --skill azure-configurator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Configure and verify post-provisioning Azure resources that are required for production-grade applications, removing fragile manual steps and ensuring secrets, RBAC, database access, and storage are correctly applied and auditable.

Core Features & Use Cases

  • Idempotent RBAC assignment and verification: check-then-create role assignments scoped to resource IDs to grant managed identities minimal privileges and avoid duplicate errors.
  • Key Vault secret upsert with verification: push sensitive env values to Key Vault using a naming conversion rule, verify read-back, and expose secrets via Key Vault reference URIs in app settings.
  • App Service, PostgreSQL, and Storage configuration: bulk apply non-sensitive and Key Vault-referenced app settings, configure PostgreSQL auth modes and required extensions, create storage containers with private access, enable soft delete/versioning, and configure CORS.
  • Operational safeguards: temporary file handling, propagation wait/retry guidance for RBAC, validation rules for database URLs, and a persistent save protocol for deliverables and review packets.
  • Use Case: finalize a CI/CD deployment by ensuring the web apps can resolve Key Vault references, the backend can reach the hardened PostgreSQL instance, and storage is configured for application uploads.

Quick Start

Use the azure-configurator skill to push .env secrets into Key Vault, assign required RBAC roles to managed identities, configure app settings with Key Vault references, set PostgreSQL auth mode and extensions, and create storage containers with CORS and verification.

Frequently Asked Questions about azure-configurator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Azure App Service settings to use Key Vault references idempotently?

To configure Azure App Service settings with Key Vault references idempotently, push sensitive environment values to Key Vault, verify the read-back, and then bulk apply the Key Vault reference URIs as app settings.

How do I assign RBAC roles to managed identities without causing duplicate assignment errors?

To assign RBAC roles to managed identities without duplicate errors, perform a check-then-create role assignment scoped to specific resource IDs, granting minimal privileges while ensuring the operation remains idempotent.

What is the best way to automate post-deployment configuration for PostgreSQL flexible servers and storage containers?

The best way to automate post-deployment configuration for PostgreSQL flexible servers and storage containers is to apply idempotent runbook scenarios that configure database auth modes, extensions, and create private storage containers with CORS.

Can I use this approach to push .env secrets directly into Azure Key Vault?

Yes, you can push .env secrets directly into Azure Key Vault by utilizing a naming conversion rule for the secret values, verifying the upsert operation with a read-back, and exposing them via reference URIs.

Does configuring Azure storage containers with this method include soft delete and versioning?

Yes, configuring Azure storage containers with this method includes enabling soft delete and versioning, alongside creating private access containers and configuring CORS for application uploads.

Why do my Azure RBAC role assignments fail to propagate immediately after creation?

Azure RBAC role assignments fail to propagate immediately after creation due to Azure's eventual consistency model, which requires implementing propagation wait and retry guidance to ensure the managed identity privileges take effect.