Hiyo Shin · Senior Designer, CoreAI

Turning validation warnings into action

Today, critical and routine warnings look the same and share one easy-to-dismiss prompt, so users and agents often proceed past a warning that will cause deployment to fail. This explores separating critical, likely-to-fail issues from routine warnings with clearer severity, structure, and prompts, so people pay attention and act instead of dismissing them.

hiyo@proto:~/workspace$ azd up
Note: Running custom 'up' workflow from azure.yaml

Provisioning Azure resources (azd provision)
Provisioning Azure resources can take some time.

Subscription: Azure SDK Developer Playground (faa080af-c1d8-40ad-9cce-e1a450ca5b57)
Location: East US 2

(!) Warning: Principal (62661785-adcf-4117-b9d0-22b3aa2b4ebf) lacks role assignment permissions on subscription faa080af-
c1d8-40ad-9cce-e1a450ca5b57
The deployment includes role assignments and will fail without Microsoft.Authorization/roleAssignments/write permission.
Suggestion: Ensure you have the 'Role Based Access Control Administrator', 'User Access Administrator', 'Owner', or a custom role
with 'Microsoft.Authorization/roleAssignments/write' assigned to your account.
(!) Warning: This warning was intentional and generated by the demo extension. Bicep snapshot contains 19 predicted resources.

? Proceed with deployment despite the warnings above?: [Y/n] Yes