I am trying to create an ASP.NET framework app in Azure so i followed the tutorial on the Azure website but while publishing there is always a problem logging in.
I have tried to login several times and it is all successful but i am unable to proceed with creating app services. The page will still be the same page asking to login or create an account.
I am also login to my visual studio 2017 enterprise with the same account so i am wondering why i can't proceed on.
Thank you
According to your description, I suppose you haven't buy the Azure. You could buy Azure from this link. After that, your account could use Azure. Then you could get Subscription for Azure portal. You could also create Resource Group and App Service Plan from Azure portal.
If you want to use Azure for free,you can use trial version.Just like the following screenshot. However, it has use time and function limit.
Related
I'm struggling to configure my Azure Web App.
I am here in Deployment Center, trying to authorize my GitHub Enterprise account:
The problem appears when I try to Authorize my account. It seems like Azure only supports Personal GitHub accounts. The Azure subscription itself is for Enterprise projects as well, yet I still can't add my GitHub. Is it even possible?
i followed this tutorial
Tutorial: Access Microsoft Graph
I can login with my organization user to the web app, but i can't use the GraphServiceClient. It always redirect me to the "signin-oidc" page with a 403 error.
Am i missing something in the tutorial? What should i check in the configurations?
Thank you in advance
According to the tutorial you provided, it requires the azure web app to enable easy-auth by azure ad, it also provides a tutorial on how to enable it.
After creating azure web app, go to Authentication then click Add identity provider, then you need to choose microsoft as the provider and then create a new azure ad app if needed. Now we can deploy sample code into azure after doing the configuration. And as the default redirect url in the code is /signin-oidc so we need to add it into azure ad authentication panel-> redirect url.
==============================UPDATE============================
If you used my sample, you also need to modify the appsetting.json with the azure ad application client id and client secret. You can use the azure ad app created just now, you only need to add redirect url with https://localhost:44321/signin-oidc and https://web_app_name.azurewebsites.net/signin-oidc. But in this sample, you don't need to enable easy-auth for azure web app. You only need to create a web app and deploy the sample code to it. I used visual studio to create and deploy. If you wanna create azure web app in azure portal, you just need to click New in azure portal->app service and complete the fields.
I created 2 LUIS apps about a month ago on eu.luis.ai, and they have been working just fine with the Bot they are linked to, but it seems that I have hit some sort of quota on LUIS requests. I think upgrading my plan to a higher tier would resolve the problem, but I can't find the app on my azure portal, and I can't find a way to change the plan from eu.luis.ai either.
You can see my LUIS apps here (eu.luis.ai)
You can see my Azure apps here, the only cognitive service appearing is QNAMaker
Does anybody have the same problem ? I am 100% sure I'm logged in with the same account on both websites.
I found what was wrong : when you first start using LUIS, you can create apps on luis.ai without creating them on your Azure portal. They come with starter keys that expire after a month or so. You then have to create a LUIS app on the Azure portal, and add the newly generated key to your existing apps.
I was having a similar problem where I had my LUIS app working with a Speech Recognition service key, and it stopped working after a month. I had to add a new LUIS service on my Azure portal and use that key instead.
I am having an issue while deploying an Azure web role to a cloud service. It shows me the error
Cloud services are not available in this subscription.
I am using a pay as you go subscription on Azure. I don't know if there is any limitation with this subscription for cloud service deployment or not.
.
Updated version of JerryGoyal's solution.
Cloud Service Management will have to be done using the new Azure Portal, because Cloud Service Management in the old portal will be disabled as of 11/15/2017.
Log into the new Azure Portal.
Go to the Subscriptions View.
Set your account as a Co-Admin. Microsoft Documentation.
I think the issue you're running into is that the Cloud Service Publish Wizard in VS only supports subscriptions in which you are an admin or co-admin granted via via the old portal (manage.windowsazure.com). If you've been given access via RBAC or the new portal, then VS will not see the resources under those subscriptions.
To work around it, you can build the package using msbuild.exe and then upload it via the portal.
That help?
Cloud services are not available in this subscription
The error is caused because the Cloud Services still use the old deployment model that is based on Azure Service Management (ASM).
To deploy an ASM based component to Azure you need to be ‘co-admin’ for the subscription.
Right now you are ‘Owner’ on the new portal but this role only has impact on the new ARM based resources.
So, just ask your subscription admin to login to the old portal (https://manage.windowsazure.com) and make you co-administrator:
Login to the old portal
Click on Settings –> Administrators
Click on the Add button at the bottom
Enter the co-admin email address and click on the OK button.
After this reload your Visual Studio and the problem will be solved.
I created an empty Azure cloud service and I want to allow other developers to deploy to it. So far the only route I can see is adding the developers as Azure subscription administrators. I would rather give them more specific access to the cloud services only.
No such functionality exist today which will allow you to grant/revoke permissions at the cloud service level. Once a developer is provided access to the subscription, they would have access to all the resources under that subscription.
There's a REST API behind cloud service deployments and all the tools (including Windows Azure Portal and Visual Studio) consume this API for creating deployments. One possible solution would be to build your own solution consuming this API. In this solution you will implement access control based on your requirements so that when your user use this service, they will only see the cloud service they're assigned to and can only manage that cloud service. There's a managed library for consuming this API. You can find more information here: http://www.bradygaster.com/post/getting-started-with-the-windows-azure-management-libraries.
It seems that if the original developer downloads the publish profile from Azure (it's an xml file that with a .PublishSettings extension), you can copy the userPWD from that file, give it to another developer and they can paste it into the password field in the Connection section of the Publish dialog.
The userPWD is a string that looks something like this:
EFFCLfDqDKHlXcA2YDZPvX4BZXWFaobxaLN0aPJd4HCfa8WxlqEkt2yywBsx