azure-web-sites

I have SQL server & web app hosted over Microsoft Azure platform. I am constantly getting above error when ever i run web application (and try to connect azure sql server) from my local network, however i never face issue on azure web app service (i.e. After hosting my web app on azure) I know that this error is very familiar. But in this case it seems weird. I have already checked below things, SQL connection is managed properly. (I am using ADO.Net) All gateway IPs are white listed against azure sql. No firewall is blocking my private network. Any help will be appreciated. From Mihaela's

I have a ASP.NET 5 site that I want to add custom error pages to. I'm used to adding entries in the web.config (from ASP.NET 4 days) but I want to use the new approach in ASP.NET 5. So I have the following in my Startup.cs class: if (env.IsEnvironment("Development")) { app.UseErrorPage(ErrorPageOptions.ShowAll); } else { app.UseStatusCodePagesWithReExecute("/Home/Error"); app.UseErrorHandler("/Home/Error"); } When I run locally using kestral my error page is displayed properly. However, when I deploy to Azure I get the very generic white error page when I try to test 404 errors: "The resource

My Azure Web Application needs to connect to various servers (both with and without SSL). This works perfectly as long as I run the application in my local IIS Express or IIS 7.5 on Windows 10. As soon as I deploy the application to Azure it stops working for certain servers that require SSL (thought not all). If I run it through ssllabs these normally get an A while the ones that work get a B or a C. So I would assume that .NET on an Azure instance supports less ciphers than I locally support or something like that? I've tried out this ServicePointManager.ServerCertificateValidationCallback =

I'm attempting to use PowerShell to assign hosts to an Azure Website instance. I've verified the domain/host I want to add is valid and even went to the Azure portal to verify it identified the new domain as valid. For some reason though, the below script is not setting the HostNames as I believe it's supposed to and when I check after setting a new value to HostNames, it's the exact same as it was before. Can someone tell me what I'm doing wrong in the script? $newHosts = @("mysite.azurewebsites.net","www.mysite.com") $result = Get-AzureWebsite -Name mysite | Set-AzureWebsite -HostNames

I am creating app which uses Identity 2.1.0 framework in .NET. I started project in Visual Studio 2015 as Empty Web App (template). Now, I use Microsoft.AspNet.WebApi.Owin , and also Microsoft.Owin.Host.SystemWeb NuGet packages in my project. I understand that OWIN is a specification made to avoid monolithic frameworks and to specify how smaller application components interact with servers. However, I have requirement to deploy to Azure App Services. I have found examples (blogs) where people deploy OWIN Web Api app as self-hosted to the Azure Cloud Services worker role. But I don't want this,

I have created an Azure Web Site and connected it to Visual Studio Online, and this automatically set up a continuous deployment build (as per this page ). Initially this worked for a solution with one project, but now I have added a Web API project as a back end. This is named such that it is the first of the two projects alphabetically , and so now it is the only project that gets built and deployed whenever files are checked in. Which leads to my question: How can I modify the default continuous deployment build to deploy both applications? I'm sure it must be a fairly simple change to

From how I understand it, the only reason a staging site would require restart is if there exists app settings or connection strings configured as slot settings. Although this doesn't always seem to be true. One of our applications will restart regardless. I have used Powershell cmdlets to be sure that there are no slot settings "hidden" from the Portal (because apparently this is a thing). What other factors can determine whether the staging site will be restarted during a swap? (I posted this on the kudu GitHub repository , but haven't heard back) EDIT: In response to Byron's answer: I have

What happens if an Azure WebJob is scheduled to run but the previous running instance hasn't finished yet? Will it run the WebJob again so that two are running at once? Will it not run the WebJob and start the clock over? I haven't been able to find this behavior documented anywhere. I have a job I want to run hourly but it's possible that sometimes it might take longer than an hour to complete, but I never want two of them running at once. As i understand it scheduled webjobs is just triggered webjobs that is run using Azure Scheduler, if you open Azure Scheduler in management portal you can