Given a VS web app project that has an existing Azure publish profile is there a way to tell what subscription the selected publish profile will publish the app to? We have such so many subscriptions it's quite time consuming to to use the portals poor blade interface to locate which subscription the app is in. Even opening the SCM site it seems apps know nothing about it's subscription.
As I know, we don't need Azure subscription information to publish our project. What we need is contentPath, ComputerName, UserName& Password when you use msdeploy. The following is the parameters that used to deploy:
.\msdeploy.exe -verb:sync -source:contentPath='E:\code' -dest:contentPath='sub2',ComputerName='https://waws-prod-sn1-047.ftp.azurewebsites.windows.net/msdeploy.axd?site=sub2',UserName='$sub2',Password='key',AuthType='Basic'
If we published project to Azure, we have no easy way to see which subscription it belongs to. I suggest you submit a voice at Azure feedback forum.
Related
With the move of Microsoft to disable the App Registration on the legacy portal we created the Bot for our MSTeams APP in Azure portal that is part of the 'Renewable E5 subscription'.But we could not able to set the Bot messaging end point url. Earlier we can able to set that from the MSTeams' App Studio's Bot section but now it is not there. https://dev.botframework.com/ asks us to create a Azure Bot service.
Is it necessary to create a Azure Bot service in order to use and set the Bot message End point ?
If not how can we set the Bot messaging End point without Azure Bot service?
It does seem, now that the functionality is removed from App Studio, that you need to work in the Azure Portal directly (that's all it was doing behind the scenes). This would require an Azure subscription, but you can use any one, so you don't necessarily require an Azure subscription for each team member.
It is important to note though, that the only thing you really need in Azure is a bot "registration". There are two options when creating a bot resource in Azure - one includes a full hosting option ("web app bot"), and associated costs (based on the options selected), and the other is just a "channel registration", which has no cost at all.
When the bot is created, you need to go to it's "Settings" screen, as shown here, where you set the messaging endpoint, but you also need to make sure to go to the "Channels" option on the left menu, and make sure Teams is added as a channel ("channel" here means a platform you want to use your bot on, like Teams, facebook, slack etc.). If your bot had been created in App Studio previously, it would not need the Teams channel added manually, but for new bots it will.
Yes, You need azure subscription. Now you can not create bot from botframework.com. Everything is moved to Azure.
So I have a single Visual studio account with 3 project in it and I have three different azure subscription for deploying these projects. But I can able to link one of the subscription to VSTS. But other two are I am not able to do linking.
I did some searching on this stuff got a link saying that it is not possible : 1
So can anybody help me on this situation.
You can only link a single subscription to a VSTS account.
That is however for paying for services for VSTS. For deployment you can setup as many connections as you like on the Services tab in the administration.
You can add as many Service Endpoints as you like then use them in Tasks in both Build and Release.
I'm trying to create a build in Team Services (Visual Studio Online) but am having a few issues.
My first step is to create a new build and I've selected the template Deployment -> Azure Web App
Then in the build step for Azure Deployment I need to select my Azure subscription. This list is currently empty so I select Manage to add a new one.
Following the instructions here I try to add a new endpoint but it says to select the one called 'Azure' but in my list I've got 'Azure Classic' and 'Azure Resource Manager'. Which one should I use?
I've tried 'Azure Resource Manager' and used the details to generate service key etc using the Powershell script as said in the previous link. Now the status just stay at 'Connecting to service using Service Principal' and is not selectable in the list.
How do I get Team Services to see my Azure subscription?
I must say, I've found the documentation for this a bit lacking in that a lot of the Microsoft sites still use the classic portal or older versions for the sites.
Starting from the end of your question, one of the reasons of that is that some functionality is not available yet on the new portal. As far as i know, all of the functionality should migrate to the new portal in a future.
For Azure Web App, please add the New Service Endpoint using classic mode (and i prefer to do that using certificate - very simple). Then, when adding the web site as the build step (for example), select your added subscription and you should be good to go.
I've created an Azure App Service application and pushed it to Azure. Unfortunately, I am unable to find the application key that I should use in my client to create the connection to the service (as seen in the below code ).
MobileService = new MobileServiceClient(
"http://xxxx.azurewebsites.net",
"applicationKeyShouldGoHere");
I've seen a few answers to this question, but all seem to point to authenticating the USER within the client. I want to authenticate the call to the service.
Azure Mobile Services had an application key but I'm unable to find the key for App services. The difficulty is multiplied with the fact that the Azure Portal seems to get modified every couple of months...
Thanks in advance.
The new Mobile App Services doesn't need/use any Key.
You need to use Version 2+ of the Microsoft.WindowsAzure.Mobile package on your client.
The older SDK created the MobileServiceClient like this:
new MobileServiceClient(applicationURL, applicationKey)
The new (Version 2+) like this:
new MobileServiceClient(applicationURL)
So there is no need for a key.
We don't publish Azure App Service in the way as we publish Mobile Services(Actually in new portal, there is no Application Key for Mobile services either).
When publishing Azure App Service, you need to download the publish profile from the portal. Right click the project in VS, and choose Publish.... In the Publish Web wizard,import the publish profile you downloaded. When the wizard completed, the App Service will be published to Azure.
Check web-sites-dotnet-get-started for details.
I currently have a Web Application and SQL Database instance published on my own personal Azure trial subscription. However the app is now finished and I want to hand ownership over to the person I am creating it for. So I want to publish it to his Azure subscription, so he can look after billing, monitor, and have ownership of the application etc.
I asked him to add me as a user to his account, and now I see his company name listed as a 'Directory' from the portals home page (along with my Default Directory, my Web App, and my SQL Database). I don't know how to proceed from here. I want to be able to Publish it from Visual Studio 2013 - then run my code first migrations to create the database, all to a location that his company and not me is responsible for.
Is my approach to this wrong? In a general sense, how do you develop a test application (and test it in Azure) and publish it for someone else on Azure?
The first comment on the question is sort of what I am trying to achieve:
Transfer all data from my account to another in the same Azure subscription
"What do you mean by from my account to another in the same Azure subscription? Normally I have seen folks want to move data from one subscription to another one (say from Dev Subscription to Prod Subscription)."
But if I just transfer the app I wouldn't be able to make changes in VS and re-publish it, for example.
EDIT:
I found this article on Migrating an enterprise web app to an Azure service. Would it be possible to Publish the app to my local dev machine (with local database), then use the Migration Assistance to move it to Azure? Obviously to do this I would need my clients Microsoft ID and password to log into his subscription which is not ideal.
You will first want to make sure that the subscription appears in your "Subscription list" in the top right corner and is selected.
I am assuming you have connected your VS with your Azure subscription and are able to publish your app to your subscription from here, and that the new subscription is "missing" from your selection. But now you have been added to a new subscription but have not updated VS. Remove and readd Azure Subscriptions from VS. This should require you to log into Azure, and should pull updated account information.
Now when you Deploy your app, you will be able to select which Subscription you want to deploy it into.