ARM

Azure deployment could not access the specified subscription

Code=SubscriptionNotFound

Azure Resource Manager could not access the specified subscription because the ID is wrong, permissions are missing, or the request is targeting the wrong scope.

SubscriptionNotFounddeployment

Observed message

Code=SubscriptionNotFound

Why it happens

The subscription ID is incorrect or malformed.
The caller does not have access to the target subscription.
A cross-scope deployment is referencing the wrong subscription context.

How to fix it

Verify the subscription GUID used in the deployment command or template.
Check that the deployment identity has access to the target subscription.
Confirm the active Azure context and cross-scope deployment parameters.

Official reference

Microsoft Learn: Common Azure deployment errors

Related errors

Explore more