**UPDATE - RESOLVED** Awareness: Some subscription-scoped deployment stacks may not be accessible

[snarkywolverine]

Around December 1, 2021, configuration was applied that made some (if not all) subscription-scoped deployment stacks inaccessible to users.

Note that this is exclusive to subscription-scoped stacks. If your deployment stack is saved in a resource group, it should be working as expected.

SYMPTOMS: Direct retrieval returns 404 Not Found - GET /subscriptions/<>/providers/Microsoft.Resources/deploymentStacks/ LIST results may return:

• HTTP 429 (if all resources were created before 12/1/21 - see issue #39)
• HTTP 200 with empty array (same as above)
• HTTP 200 with some - or all - of the deployment stacks listed. Note that, just because the deployment stack shows up in the list call, does not necessarily mean it will be accessible via "point GET"/direct retrieval above.

We are aware of the issue and actively working to correct it; no action is required by the user to resolve this situation at this time. Also note that the stack itself is not affected; only the retrieval of the stack.

If you need to access a deployment stack, and it is unavailable - you can re-PUT the stack, which will attempt to redeploy the template and restore access to the stack (and all of the prior snapshots).

[snarkywolverine]

This should now be resolved for all customers, where telemetry indicated a subscription-scoped stack may have been impacted.

If your subscription was missed for some reason, please update this issue with your subscription ID, or reach out to me directly.

Thank you for your patience.

(This will be closed around 3/11/22, to give people an opportunity to see the issue was resolved.)