azure-app-service-envrmnt

Azure LocalCache not setting the Ready environment variable on ASE

北城余情 提交于 2019-12-06 03:05:19
I have moved my WebApp to the Azure App Service Environment and have enabled the new LocalCache option as documented at https://azure.microsoft.com/en-us/documentation/articles/app-service-local-cache/ However, the environment variable that is supposed to tell you that the cache is ready does not exist. If I use Kudo and go to Process Explorer, Click on properties for the w3wp (without the scm label) process, then click on Environment Variables the only variables I see are: WEBSITE_LOCAL_CACHE_OPTION Always APPSETTING_WEBSITE_LOCAL_CACHE_OPTION Always WEBSITE_LOCAL_CACHE_SIZEINMB 1000

How to configure Azure AD to enable refresh tokens

房东的猫 提交于 2019-12-05 04:57:31
问题 I have an Azure App Service / Web API linked to Azure AD and authentication is working, however client tokens are expiring after 1 hour, so I want to enable the OAuth refresh_token. When I inspect the results of calling /.auth/me on my service I don't see a refresh_token. Token store is enabled on the app service. I have tried to add it to the oauth2permissions in the Azure AD manifest as follows, but it doesn't appear (I have restarted the App service and redeployed my service in case of

How to restart Azure App Service Instance

强颜欢笑 提交于 2019-12-04 00:09:40
I have an Azure App Service that contains 1 Web App with 1 slot. I have 2 instances assigned to the App Service. This week, the App Service shows about 60% CPU usage, and its usually about 10-15%. Upon further investigation, it looks like 1 of the two instances is maxed out. When opening up the Site Metrics per Instance, I can see that HTTP Response times are in the 1000s of milliseconds for one instance, and less than 200ms for the other. I have tried restarting the W3P process on the offending instance, but that doesn't seem to help. I have also tried scaling up to additional instances. The

How to configure Azure AD to enable refresh tokens

蹲街弑〆低调 提交于 2019-12-03 20:27:39
I have an Azure App Service / Web API linked to Azure AD and authentication is working, however client tokens are expiring after 1 hour, so I want to enable the OAuth refresh_token. When I inspect the results of calling /.auth/me on my service I don't see a refresh_token. Token store is enabled on the app service. I have tried to add it to the oauth2permissions in the Azure AD manifest as follows, but it doesn't appear (I have restarted the App service and redeployed my service in case of caching of tokens) : "oauth2Permissions": [ { "adminConsentDescription": "Allow the application to store a

Azure App Service vs Azure Service Fabric [closed]

偶尔善良 提交于 2019-12-02 17:51:40
Can anyone direct me to something that will explain when I should create an Azure Service Fabric application vs an Azure App Service application? I have an application I want to build but can not determine whether I should build it using the Azure Service Fabric or the Azure App Service. Microsoft has created the document with a comparison for Azure App Service, Virtual Machines, Service Fabric, and Cloud Services. Also, you might find helpful this decision tree. Unfortunately there isn't any official guidance about when to use what. They're two separate platforms, following different

Azure App Service - Custom Authentication - HTTP Verb not allowed

╄→гoц情女王★ 提交于 2019-12-02 06:02:57
I followed this tutorial to enable authentication in my Xamarin.Forms App: https://adrianhall.github.io/develop-mobile-apps-with-csharp-and-azure/chapter2/custom/ A test with Postman (as described in the tutorial) went succesfully. The token returned. When i call this from my C# code... LoginAsync("custom", Newtonsoft.Json.Linq.JObject.FromObject(auth)); I got an error like: Method not allowed. HTTP Verb not allowed I found out that the Azure SDK sends a POST and GET request when calling LoginAsync. So i changed this... [HttpPost, Route(".auth/login/custom")] public IHttpActionResult Post(

Only getting Your App Service app has been created - after deploying to azure

我是研究僧i 提交于 2019-12-01 16:55:20
问题 After I deploy a web api to azure, I get the screen: Your App Service app has been created Go to your app's Quick Start guide in the Azure portal to get started or read our deployment documentation. I try to access some of the api/controller end points but then I get the message: "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable." Does this take a while to start on or shouldn't it work straight away? Thanks 来源: https://stackoverflow.com

How to check Azure Network Security Group outbound IP Allowed or not?

邮差的信 提交于 2019-11-29 12:43:14
I have few problems regarding Azure Network Security Group. Currently I'm using Azure App Services to publish my website and in Azure, App Services, Network Side Controlled By NSG such as inbound and outbound security and other things. I'm working with sagepay payment gateway.they asked me to do following steps in order to success my sagepay integration. Please ensure that all of the following IP addresses are allowed within your Server or Firewall: For outbound traffic to our gateway: 195.170.169.9 – live.sagepay.com 195.170.169.8 – test.sagepay.com For inbound traffic you only need to

Where is the key in new Azure App service?

亡梦爱人 提交于 2019-11-28 13:35:09
While using the classic Azure Mobile services, you used to get a key along with a URL for your Mobile Service app. This key was also used to explore the APIs on your backend site & was used as a password. With new Azure App services all you need to instntiate the mobile service client is the URL like below private static readonly MobileServiceClient MobileService = new MobileServiceClient("https://thecityapp.club"); There is no key *a second parameter that was available with Azure Mobile services. What is now used as password to explore the APIs on the web? Supreet, With App Services/Mobile

Where is the key in new Azure App service?

Deadly 提交于 2019-11-27 07:54:28
问题 While using the classic Azure Mobile services, you used to get a key along with a URL for your Mobile Service app. This key was also used to explore the APIs on your backend site & was used as a password. With new Azure App services all you need to instntiate the mobile service client is the URL like below private static readonly MobileServiceClient MobileService = new MobileServiceClient("https://thecityapp.club"); There is no key *a second parameter that was available with Azure Mobile