azure-web-sites

I do have a simple .Net Core web api application, the one made by Visual Studio when a new project is created. I want to deploy it to an Azure App Service via FTP (part of a TFS 2017 build job), which is successful: However, when trying a GET like http://somerandomname.azurewebsites.net/api/values all I get is a 404 with the text The resource you are looking for has been removed, had its name changed, or is temporarily unavailable. From Kudu I get the following error: What am I missing? So a web.config is needed. The one which VS 2017 populates with some default values when a new item is added

I am trying to implement an architecture that follows the OAUTH2/OIDC protocol. In order to do that, I have STS(Identity Server v3 by leastprivilege), ASP.NET WebApi and ASP.NET MVC application for a client. My goal was to have the STS and REST service hosted on Azure so different clients can use them as public services. So far so good. Everything seemed to work smoothly and perfectly before I decided to add a new client that uses one of the redirection flows - Authorization Code flow. I wanted to take advantage of the refresh token option that it offers. I wanted to serve short life access

For a website my team are currently working on we're trying to write some PowerShell automation to temporarily override a connection string which is otherwise usually in Web.config, and then at a later point delete it. However, using both the PowerShell cmdlets and the Azure REST APIs, we don't seem to be able to ever reset the connection strings set to be empty. Whenever we try to delete it either the command says it succeeds but doesn't delete it, or the requests is rejected as invalid. It's possible to delete all the connection strings using the Management Portal, so what are we missing

I have an asp.net mvc website that I'd like to deploy to Azure (preferably via GitHub deployment) so that it's accessed as subfolder of the main domain. e.g. http://example.com/mymvcsite/ Ideally I'd like the website to be completely self-contained under the subfolder. As if it was configured to be a good old-fashioned IIS application folder. Ie I don't wanty to build a domain mvc website for mydomain.com that just happens to do all it's business under the /mymvcsite/ subfolder path. I'm quite happy for the entire website to be hosted on Azure, it just makes sense for this particular project

I am planning to use Azure Traffic manager to do a failover of my app running on one Azure zone to Azure zone. I need some suggestion, if that is the correct approach to do a failover ? We have seen issue with Azure that, most of the services in one region goes down for few hours. Although I understand that Azure traffic manager is not associated with the region. But is it possible that Azure traffic manager goes down or that traffic manager endpoint is not reachable although my backend webapp is reachable? If I am planning to use Azure traffic manager, what are other problems I should be

In my Azure App Service I want to update application settings, but after publish from VS the keys doesn't override values from local Web.config In Azure it looks like: In the result my web.config on azure contains values from local settings <connectionStrings> <add name="MainConnectionString" connectionString="ConnectionStringToReplaceByAzure" providerName="System.Data.SqlClient" /> </connectionStrings> <appSettings> <add key="MS_SigningKey" value="Overridden by portal settings" /> </appSettings> Azure never physically modifies your web.config file. Instead, the Azure App Setting is injected

Note: This is different from the question of detecting running locally versus in an Azure role, which I understand has been answered already. I've got an APS.NET MVC app which I deploy to Azure. I'm running V2.5 of the Azure tooling. I'd like to be able to detect which of the following three scenarios the code is running in: Locally (debugging on IIS), Azure website or Azure web role I've seen in other posts the suggestion to use the following: RoleEnvironment.IsAvailable However, this seems to be an incomplete solution for my needs. It seems to detect if the code is running locally or as a

From the looks of it the new Azure Websites Feature still does not support hosting them under a naked domain such as example.com instead of www.example.com. Am I missing something? Azure Websites have now released support for naked domains. Websites that are run on Shared or Reserved instances does support naked domains through an A record. Domain management is available through the Azure management portal. Update 2012-10-21: I previously stated that free instances could rely on CNAME to redirect a subdomain to their free Azure-website, but this appear to be incorrect, at least at the moment.

I have a ASP.NET 5 website with 3 subprojects. The subprojects have a reference to EF 6.1. Locally everything works fine, but when I try to deploy the website to azure using the assistant, I get the error message Dependency EntityFramework >= 6.1.3 could not be resolved in XXX\wrap\PDWeb.Application\project.json 22 The generated project.json of the PDWeb.Application subproject is { "version": "1.0.0-*", "frameworks": { "net452": { "wrappedProject": "../../Application/PDWeb.Application/PDWeb.Application.csproj", "bin": { "assembly": "../../Application/PDWeb.Application/obj/{configuration}/PDWeb