# Look in Activity Log when SKU validation leaves no deployment history

> A template can fail SKU validation before a deployment starts, leaving evidence outside the deployment-history view.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-249-look-in-activity-log-when-sku-validation-leaves-no-deployment-history/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:27:47+00:00
- Modified: 2026-09-10T01:20:46+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

A template can fail SKU validation before a deployment starts, leaving evidence outside the deployment-history view.

## Potentially affected

Azure ARM or Bicep deployments rejected because a requested SKU is unavailable for the selected subscription, location or zone.

## DSE recommendation

Capture the Activity Log validation error and exact requested SKU scope before changing the deployment.

## Article

## Source facts

Microsoft documents that an ARM or Bicep deployment can fail SKU validation before execution begins. In that case, InvalidTemplateDeployment appears with an error message, no deployment history is created, and the error is available in the portal’s Activity Log.

SKU availability must be checked for the subscription’s selected location or zone. The documented CLI availability listing hides restricted SKUs by default; its –all option includes those restrictions in the review. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-sku-not-available).

## Applicability

Record the subscription, region, zone, requested resource SKU and original validation response. Keep a predeployment validation failure distinct from a resource that began provisioning and failed later.

## DSE recommendation

DSE recommends preserving the Activity Log evidence before retrying with different settings. Review the actual restriction information and the workload’s placement requirements together. Do not choose an arbitrary region or smaller size merely to make validation pass. If the required placement has no suitable available SKU, route the documented requirement through the appropriate support or architecture decision.

## Verification

Compare the planned SKU and placement with the current subscription-specific listing, including restrictions. After an approved adjustment, rerun validation and confirm whether deployment actually starts. Preserve both the original rejection and the new outcome. A missing deployment-history entry should not be recorded as proof that no request was attempted, and a passed validation should not replace subsequent workload verification.

## Official references

[Microsoft Learn: SKU not available errors](https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-sku-not-available). Source retrieved September 9, 2026.

## Primary reference

- Name: SKU not available errors - Azure Resource Manager | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-sku-not-available
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Look in Activity Log when SKU validation leaves no deployment history,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-249-look-in-activity-log-when-sku-validation-leaves-no-deployment-history/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.