You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2023. It is now read-only.
Based on the current information, unfortunately, the only thing I could interpret is that the ARM template seems to have faced some issue in deploying the KeyVault resource in your chosen deployment. You could consider trying to re-deploy the same RG/Identity/AppName combination by simply re-executing run.bat or deploy a new RG inside a different region than the one tried above.
Troubleshooting Tips
In order to understand the issue in more detail, one way could be to go through the deployment details which could be accessed via Azure Portal.
Go to Azure Portal -> Choose appropriate Subscription -> Select Resource Groups blade from Left Rail -> Choose appropriate Resource Group -> Select Deployments Blade from Left Rail.
In case none of the above help you move in the correct direction, I'd request you to please reach out to us at learnlti@microsoft.com in order to better understand your issue and provide support from our end.
Bug
Parent Resource Not Found
Deployment failing in Step 8 - Creating Resources in Azure within PowerShell.
To Reproduce
Steps to reproduce the behavior:
"error": {
"code": "ParentResourceNotFound",
"message": "Can not perform requested operation on nested resource. Parent resource 'kv-73i32pmz3' not found."
}
}
Additional context
This occurred after pulling Main to fix the HTTPSConnectionPool which was corrected in the azuredeploy.json
The text was updated successfully, but these errors were encountered: