Portal Links

The %2F encoding is critical and models consistently decode it back to / during text generation, producing broken links. Always use .Replace('/', '%2F').

Read LINK= from terminal output and print the URL in chat on its own bare line — no backticks, no markdown. Then deploy:

RG-scope (403 fallback)

Use az deployment group create --name $deploymentName --resource-group {rg} and adjust $resId to include /resourceGroups/{rg}:

For Terraform (no single ARM deployment): https://portal.azure.com/#@{tenantId}/resource/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/activitylog

💡 Resolve {subscriptionId} and {resourceGroup} from context.json. For Terraform, resolve {tenantId} via az account show --query tenantId -o tsv.

Same-Scope Retries vs New Names

The portal link stays valid for same-scope retries — ARM overwrites in-place. Generate a new name (e.g., $deploymentName = "app-onboard-deploy-{first8}-2") only when scope or RG changes.

Chat Output Rules

1. Terminal command: the PowerShell snippet above (outputs the bare URL and auto-opens it in the default browser via Start-Process)
2. Read the terminal output — find the line starting with LINK= and extract the URL
3. Chat output: paste the bare URL on its own line — no backticks, no markdown, no emoji on the same line

⛔ Link must be ctrl+clickable. The URL MUST be the ONLY content on its line — no emoji, no text, no backticks, no markdown formatting, no markdown link syntax on the same line. Terminals auto-linkify bare URLs but ONLY when the URL is alone on the line.

⛔ Emit a NEW link whenever deployment name changes. When healing causes a redeploy with a different --name, you MUST re-run the PowerShell snippet with the new name and print the new link: