azure-web-sites

I have a website running as a web app on a dedicated Azure plan. It connects to a Redis, SQL Azure and a MongoDB backend. The website has been running fine for weeks now and then without any new code I am now getting lots of socket exceptions starting like the one below. An attempt was made to access a socket in a way forbidden by its access permissions. The website intermittently gets the error when connecting to Redis, SQL Azure and MongoDB which makes no sense. I changed the Pricing Tier for the site which would move the website from one VM to another behind the scenes and the errors went

I am trying to wrap my head around the concept of Azure App Service plan and Azure App Services, with no luck. My understanding is that an App Service Plan defines the capacity and the pricing, all apps assigned to a specific App Service plan will share the same resources, is that right? If that is right, then what is the benefit of the scaling-out? If the scale out will create more instances of the same app which at the end will be hosted on the same App Service Plan (sharing the same resources)? I read almost all the official and non-official documentation about Azure App Service plan and

My goal is to secure my mobile app custom API methods and use then via httpclient(c#). As a part of the testing I used Postman to request a token and use it to access the resource. Avinash Gadiraju I will explain with the vanilla template that comes when creating a new Mobile App. Create a new mobile app. Publish it to Azure. Open it on Azure portal, Go to Settings blade. Find Authentication / Authorization . Turn App Service Authentication to On and select Azure Active Directory>Express>Create a new AD app . Open Active Directory (Management Portal), pick the directory for your account.

I am publishing an Azure Web App, and I'm running into a strange issue executing code first migrations. The remote connection string for this database is working just fine if I do not check "Execute Code First Migrations". However, if I check the box, a strange connection string with a curious misspelling, "ConnetionString", gets injected into the remote web.config: <add name="DbContext_DatabasePublish" connectionString="DbContext_DatabasePublish.ConnetionString" providerName="System.Data.SqlClient" /> This, of course, is not a valid connection string and the EF initializer throws this

I am having several node js script files.I have to run these js files in azure web jobs.can any one tell me the detail step for how to add the node.js files in azure web jobs and also how to run these web jobs. If you have a file with a .js extension it'll be run as a node program Full documentation on Azure Web Jobs here: https://azure.microsoft.com/en-us/documentation/articles/web-sites-create-web-jobs/ It's relatively easy if you know some undocumented details :) The key concept is ensuring correct application structure (for Azure). Your main application script should be named run.js , so

I'm trying to use Azure Web Apps (Linux) to host a basic static site. I configured everything so a new deployment happens with every Git push. I put my pre-built pages in my repo to confirm everything works fine with this setup. Now I've removed the pre-built pages and kept only the templates and the build script (which is basically just an npm install and a mustatic 'compile') and I'd like to run this build script in my web app. I've scoured the internet but can't find anything. How can I run a script upon first deployment and after each Git-push-triggered deployment? How can I run a script