# Azure Compute API will always return a VM security type > A new Compute API version removes nullable securityType responses, requiring clients to treat Standard as an explicit value rather than an omission. Canonical URL: https://www.devobs.io/news/news-azure-compute-api-securitytype-non-null/ By: Jonah Reed Published: 2026-09-06T11:58:54.637Z Updated: 2026-09-06T11:58:54.637Z Event date: 2026-03-09 Section: Infrastructure Microsoft announced that Compute API version 2025-11-01 will always return a value for a VM or scale set's `securityType`. When a request omits the field or sends null, Azure will return `Standard`; explicit `TrustedLaunch` and `ConfidentialVM` values keep their meaning. The [Compute team says](https://techcommunity.microsoft.com/blog/azurecompute/upcoming-compute-api-change-always-return-non-null-securitytype/4500387) this response change does not alter runtime configuration. ## Why the contract matters Inventory systems often assign meaning to absence. A collector that treats null as “unknown” may classify the same machine as Standard after adopting the new version. Code that assumes the field is optional can instead simplify around the documented enum. Older API versions remain unaffected, so callers using different versions may temporarily report one estate differently. This is a schema migration, not a security rollout. The practical risk sits in deserializers, compliance rules, and update loops that compare desired null with returned Standard. ## Check consumers before upgrading Search code and dashboards for null checks around `securityProfile.securityType`. Add fixtures for Standard, Trusted Launch, and Confidential VM, then compare fleet totals across API versions. If automation deliberately sends null, verify the explicit response does not trigger repeated writes. Pin API versions in infrastructure tooling and document Standard in internal reports. Update schemas that allow arbitrary strings, while preserving a safe path for future enum members. These steps make the upgrade observable and keep response normalization from looking like configuration drift. ## Source references -