azure-platform-stack

Automate Azure infrastructure provisioning with deterministic naming and RBAC-first security.

Updated Jan 12, 2026

Search Tags:#azure #rbac #mcp #infrastructure #terraform #deterministic-naming #uuidv5

Ready to run

npx skills add https://github.com/orafaelferreiraa/platform-as-a-service-stack --skill azure-platform-stack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: azure-platform-stack
Source: https://github.com/orafaelferreiraa/platform-as-a-service-stack/tree/main/.github/skills/azure-platform-stack
Command: npx skills add https://github.com/orafaelferreiraa/platform-as-a-service-stack --skill azure-platform-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Azure infrastructure provisioning often suffers from inconsistent naming, weak RBAC, and governance gaps. This skill enforces deterministic naming, RBAC-first security, feature-flag orchestration, and Microsoft Docs/MCP-aligned practices to reduce drift and security risk.

Core Features & Use Cases

Deterministic naming with MD5 suffixes for globally unique resource names.
UUIDv5-based role assignments and time-based RBAC propagation to ensure idempotent security.
Feature-flag driven deployment patterns and multi-subscription governance for complex Azure environments.
Observability and secure by-default configurations (RBAC-enabled Key Vault, Storage, etc.) aligned to Platform Stack standards.
MCP validation workflow integration to verify provider versions and docs before implementation.

Quick Start

Provide an Azure platform configuration outline that uses MD5-based deterministic naming, uuidv5 RBAC role assignments, and RBAC-first security for a v3.0.0+ stack.

Frequently Asked Questions about azure-platform-stack

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

FAQPage Schema

How do I enforce deterministic naming for Azure infrastructure across multiple subscriptions?▼

Deterministic naming for Azure infrastructure uses MD5 suffixes to generate globally unique resource names, ensuring consistency and reducing drift across multi-subscription environments. This approach enforces unique IDs and proper RBAC propagation without manual naming conflicts.

What is the best way to automate RBAC role assignments in Azure with Terraform?▼

RBAC role assignments in Azure are automated using UUIDv5-based identifiers for idempotent security. This method enforces time-based RBAC propagation delays of 180 seconds, ensuring permissions are fully applied before dependent resources are provisioned.

Why does my Azure RBAC role assignment fail immediately after resource creation?▼

Azure RBAC role assignment fails because permissions require a propagation delay before taking effect. Enforcing a 180-second RBAC delay after resource creation ensures the security principal is fully applied, preventing immediate downstream access errors.

Does this Azure platform stack approach work with MCP validation workflows?▼

This Azure platform stack approach integrates with MCP validation workflows to verify provider versions and documentation before implementation. It enforces platform stack pattern compliance, ensuring infrastructure deployments meet Microsoft Docs alignment and feature-flag dependency checks.

When do I need feature-flag driven deployment patterns for Azure PaaS environments?▼

Feature-flag driven deployment patterns are needed for Azure PaaS environments when orchestrating complex multi-subscription governance and managing feature-flag dependencies. This ensures secure by-default configurations for RBAC-enabled Key Vault and Storage, aligned to Platform Stack standards.

Can I use uuidv5 for idempotent role assignments in v3.0.0+ Azure platform stacks?▼

UUIDv5 is used for idempotent role assignments in v3.0.0+ Azure platform stacks to generate deterministic role assignment IDs. This ensures security configurations are consistently applied across storage, keys, and container workloads without duplicate role creation.