secure-defaults

This Skill enforces mandatory security rules for Azure project creation by prioritizing managed identity, RBAC role assignments, and credential-free authentication, actively overriding insecure patterns like connection strings, account keys, and admin passwords.

To prevent connection strings and account keys in Azure SDK code, enforce credential-free authentication patterns that override upstream insecure service references. This ensures all generated application code adheres to mandatory security best practices using managed identities.

Yes, secure-defaults is invoked automatically by azure-manager, azure-architect, and azure-dev agents during Bicep generation and SDK code generation to ensure every new Azure project adheres to mandatory security configurations.

The best way to apply credential-free authentication across new Azure projects is to enforce mandatory security rules that prioritize managed identity and RBAC role assignments, actively preventing the use of connection strings, account keys, and admin passwords.

Your Azure Bicep deployment might use admin passwords and access keys due to default insecure patterns from upstream service references. Enforcing mandatory security rules overrides these patterns to ensure managed identity and RBAC are used instead.