Shared Azure AI Operations
Model migration in one day, coordinated key rotation, alerts managed as code and a Node.js security patch sweep across AI apps.
Key results
23 deployments
New model deployments created in 12 resource groups within one day
24 rotations
Key regenerations completed over two weeks
22 rules
Alert rules maintained in code
- Azure AI operator
- Aug 2026 to Oct 2026
- Project
- L3:azure-ai-operations
Results
23 deployments
New model deployments created in 12 resource groups within one day
24 rotations
Key regenerations completed over two weeks
22 rules
Alert rules maintained in code
9 repos
Repositories patched for the October 2026 Node.js security release within two days
Problem
AI applications shared one subscription and needed coordinated model retirement migrations, key rotation and a move away from portal-managed alerts.
Contribution
- I migrated models across company resource groups in one day and retired the old deployments.
- I rotated keys as apps moved to Key Vault references, put alert rules into code and captured rollback snapshots before high-risk cut-overs.
- When the October 2026 Node.js security release landed before App Service images caught up, I merged dependency fixes in 9 repositories within two days and proposed signature-verified bundled runtimes as a reversible stopgap; most runtime PRs still await merge, and one runs in production after smoke checks.
Tech stack
Azure Resource Manager
Azure AI Foundry
Key Vault
Log Analytics
Application Insights
Container Apps
App Service
Cosmos DB
More AI Engineering projects
Technical Consultant, Software & AI, Metrodata (PT Mitra Integrasi Informatika)