Three months with Azure Data Manager for Energy: the gotchas Microsoft's docs won't tell you
TechPreacher · x · 2026-09-26
Microsoft's Forward Deployed Engineering team shares a hands-on retrospective after three months building a data platform on Azure Data Manager for Energy (Microsoft's managed OSDU service), with every finding verified on a live instance.
Key gotchas
- Provisioning is a one-shot decision: instance name (1-15 lowercase alphanumerics), region, SKU, data partition names and the networking model are effectively permanent; changing region means full redeploy plus data migration. Provisioning takes up to 2 hours (measured 1h43m) — don't cancel it.
- Regional capacity is finite: they needed 5 attempts across 3 regions before finding one with backend capacity. A failed ARM deployment still leaves a live resource in Failed state — delete it (Microsoft.OpenEnergyPlatform/energyServices) and confirm no lingering ME managed resource groups before retrying.
- Identity: each instance needs its own Entra app registration whose application id becomes the unchangeable data-plane instance id; app id + client secret is admin access to everything, so plan rotation and vaulting upfront.
The writeup also covers entitlements, schemas, OSDU Search behavior, ingestion via Azure Data Factory, and operations — the checklist they wish they'd had on day one.
More from Infra
- Running Qwen2.5-Coder-3B on Android: Jupyter + Pydantic Evals on-device eval pipeline — alex_b3b · 2026-11-11
- 22% of Nvidia revenue now books to Singapore, but only ~1% is local buyers — Gregory_C_Allen · 2026-11-11
- Huawei's Kirin 9050 NPU claims offline 30B MoE on smartphones, +140% perf — AIFlow_ML · 2026-11-11
- Stratechery: Intel vs AMD's diverging earnings and Intel's need for an old-new path — Stratechery · 2026-11-11
- a16z Podcast: Mike Volpi on What the 1990s Internet Boom Teaches Us About the AI Buildout — a16z Podcast · 2026-11-11
- Alibaba files to list chip-design unit T-Head in Hong Kong to fund AI push — pstAsiatech · 2026-11-11