Unable to Publish bot

I have a Bot built in Framework Composer. I have an existing subscription in Azure with what I believe to be all the right resources however when publishing using existing resources I am continually getting this error:

---
"{\"name\":\"DEPLOY_ZIP_ERROR\",\"message\":\"There was a problem publishing bot assets (zip deploy). {\\\"stack\\\":\\\"Error: getaddrinfo ENOTFOUND mks1cpm-chatbot.scm.azurewebsites.net\\\\n    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:60:26)\\\",\\\"message\\\":\\\"getaddrinfo ENOTFOUND mks1cpm-chatbot.scm.azurewebsites.net\\\",\\\"code\\\":\\\"ENOTFOUND\\\",\\\"config\\\":{}}\",\"stack\":\"Error\\n    at new CustomizeError (C:\\\\Users\\\\nfrancis\\\\AppData\\\\Local\\\\Programs\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\extensions\\\\azurePublish\\\\dist\\\\extension.js:276418:25)\\n    at createCustomizeError (C:\\\\Users\\\\nfrancis\\\\AppData\\\\Local\\\\Programs\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\extensions\\\\azurePublish\\\\dist\\\\extension.js:276423:10)\\n    at BotProjectDeploy.deployZip (C:\\\\Users\\\\nfrancis\\\\AppData\\\\Local\\\\Programs\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\extensions\\\\azurePublish\\\\dist\\\\extension.js:276954:13)\"}"
---

---
"DEPLOY_ZIP_ERROR - There was a problem publishing bot assets (zip deploy). {\"stack\":\"Error: getaddrinfo ENOTFOUND mks1cpm-chatbot.scm.azurewebsites.net\\n    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:60:26)\",\"message\":\"getaddrinfo ENOTFOUND mks1cpm-chatbot.scm.azurewebsites.net\",\"code\":\"ENOTFOUND\",\"config\":{}}"

One question I have is if a Web App resource is needed for successful deployment?

Would appreciate any help that can be given!

FYI I am working within an Azure tenant that has limited my permissions & rights. I can create Web Apps but have no access to Azure AD or Apps…

[nickfrancis]

Thanks for the help Anish 😃

[anishprasad01]

Hmm, yeah, if that’s the case, it’s likely there’s nothing we can do about it. Looks like you will need to reach out to your tenant admin and request a permissions elevation. If your permissions are supposed to be enough, you would then need to turn to Azure Support. We manage the SDK, but we don’t have control over Azure permissions.

That said, since this is outside of our scope, I’m going to go ahead and close this issue. If you have further issues after you get your permissions sorted out, please feel free to open a ticket in the appropriate repository.