azure-web-sites

I'm exploring Azure but unable to figure out how to allow my App service to connect to the VNET I created so it can access the HDInsight cluster. My scenario is this, I'm running a Kafka HDInsight cluster deployed in the VNET I created and I need to also deploy my Azure Web App for Container in the same VNET so it can connect to the Kafka brokers. I haven't seen a good documentation on this, need help on how to set the Azure app service to connect to my VNET over a private network? The Network is disabled (don't know why) on my App service. Thanks VNET integration is not available yet for Web

We have a system that is based on 2 tiers, a Backend tier and a Frontend tier, right now both are Azure WebSites communicating trough WebAPI. I wan't to move the backend WebAPI to API App - question is - if it's possible to configure the security of an API App in such way, that it is only accessible from the configured Frontend ASP.NET MVC 6 Web application (hosted in Azure WebSites). We planned to use Active Directory as an authentication method between the frontend Web App and the backend Web App, so that only the frontend can have access to the backend WebAPI. Is this the most secure way?

According to this semi-official answer here, Azure websites now supports .NET 4.5.2: https://stackoverflow.com/a/23554969/68231 However, when I visit the Kudu debug console, it doesn't show that .NET 4.5.2 is installed: And indeed, when I try to push out a website targeted to .NET 4.5.2, Kudu refuses to build and deploy the website in question, with errors like this: Areas\Integration\Controllers\TwitterController.cs(18,31): error CS0012: The type 'System.Object' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Runtime, Version=4.0.0.0, Culture

I deployed a ASP.NET MVC4 app with SQL Server CE database, but I'm getting Sorry, an error occurred while processing your request I am using VS2012 to publish this app to azure website. How can I solve this issue? Thanks. To summarize and so an answer can get marked on this to help the next person that comes by. When running into issues on azure-web-sites FTP is a handy debugging tool which enables you to: Verify that the dll exists in your bin directory Sometimes the .gitignore file blocks directories from being checked in Verify that your web.config file has the proper version of the

I have a Windows Azure Website (built with ASP.NET Web Pages), and in the configuration have enabled "Application Diagnostics" for both Blob storage and file storage: I've then added some Trace statements to a Razor page to test it out @{ System.Diagnostics.Trace.TraceInformation("INFORMATION"); System.Diagnostics.Trace.TraceWarning("WARNING"); System.Diagnostics.Trace.TraceError("ERROR"); } However, this results in no logs at all, either in the file system or the blob. For good measure I attempted to add various settings to my web.config file (shown below), although from the documentation I

Question structure: First I give structure and configs of my ASP-MVC-4 project, then describe how I deploy my site to Azure Web Apps and finally present my error and question. My problem is related to conflicts with EF Code-First Migrations during Azure Deploy. My ASP MVC 4 Project and configs: I'm using Visual Studio 2015-U3 . I've ASP.NET MVC 4 website. Target framework: .NET Framework 4.5 . The site have its own database and works locally and interacts with database ( (LocalDb)\v11.0 ). I was using Entity Framework Code-First approach to create and fill data. My DB connection string in Web

For a long time I've been managing an Azure web site in testing, staging and production environments. Initially, all of them were free and I noticed the server sometimes was very slow to respond to async requests. Some requests took 15-30 seconds to complete on the Azure web site. A local copy running on IIS worked with no problem and request times ranged from 75ms to 400ms. At first I thought the problem with the Azure websites was the 'Always on' feature but after upgrading the production server to a Standard 2 level the exact same problems still exist. Recently I ran a profile with