@Arghya We understand your app works locally but once deployed to Azure, it gives an error.
There are a number of reasons as to why this error can occur. We will list a few of them below to see if any of them align with your specific situation.
- Database misconfiguration. In the past customers receive this error when attempting to connect to an on-prem DB and using the FQDN. You do not want to use the FQDN on your application string or hybrid manager profile. Just put the database name is all that is needed.
- Does your app contain any logging? This might help see if there is a dependency not loading and thus, a custom startup script would be helpful.
Please let us know the outcome of the two common scenarios. If you have further questions, please reply here so we can assist you further.