I'm having trouble connecting my Azure Web App to my Azure DevOps organization.
I somehow managed to do it for one Web App (by selecting creating a new 'DevOps Project') but now struggle at setting a new WebApp to link to that same DevOps pipeline. (The goal is to have a two stages delivery pipeline, which requires 2 webapps: one for QA, the other for Prod).
When creating a new WebApp, I go to Deployment Center > Azure Repos > Azure Pipelines (Preview) and get the following error message : "You do not have any valid Azure DevOps organization".
Any idea how to make that work? Note: I tried creating WebApps with same resource group and same App Service Plan and doesn't work.
Thanks a lot for any help.
Best
Lucas
UPDATE: The issue here is having Azure Portal "see" the DevOps organization.
Seems to be an account issue: you know how one has two options in account?
Pretty sure it has something to do with the Azure Portal and DevOps being on different account "directories": "Default Directory" VS "Microsoft Account". But still can't explain the behaviour....
I encountered the same "You do not have any valid Azure DevOps organization" message. I solved it by going to the Visual Studio Marketplace and enabling billing for our visualstudio.com repo for Microsoft-hosted CI/CD. Some documentation says DevOps (Azure Pipelines) is free for 5 users, I'm guessing we didn't qualify because we have 6 active users in our Azure Devops (visualstudio.com) repo. (We recently had to break out the credit card to enable a 6th team member.)
Here are the steps I used to get to the marketplace and enable billing:
In the Azure Portal, click "All services" then search for "devops".
Click "Azure DevOps organizations"
Our visualstudio.com (aka Azure DevOps, the service formerly known as VSTS) project repo was displayed in the results. Click on it.
A summary display appeared with "Setings | Remove billing | Set up billing | Connect AAD ..." along the top. In lower right of the summary area, click "All settings =>". An "Organization settings" blade (column) displays on the right.
In the "Organization settings" blade, click "Azure Pipelines". In our case, the display showed "MICROSOFT-HOSTED CI/CD" with "0 Edit" beneath, and SELF-HOSTED CI/CD with "1 Edit" beneath. The Self-Hosting doesn't apply to us, so...
Click "Edit" for the Microsoft hosted CI/CD item.
You will be taken to marketplace.visualstudio.com with "Microsoft-hosted CI/CD" displayed on the left and a screen where you can select the number of "Paid parallel jobs". In our case, we use a 3rd party service for our Microsoft licensing, so I wasn't able to see what the Total cost would be. But I chose 1 parallel job and continued through the process. Once I'd enabled billing, I was then able to go back into the Azure Portal and (after refresh) make it into the process of setting up a build pipeline as per the various videos and documentation.
As is so often the case with Microsoft, the initial "You do not have any valid Azure DevOps organization" message was not helpful, the process nothing like the smoke-and-mirror demos, and wording like "free for 5 users" misleading.
Hopefully the above will work as it did for me and save others some time.
Related
I can't see all my Github organization repositories in the dropdown of Azure deployment center. Azure was already authorized long time ago and the dropdown was showing all the repos correctly until last week when I was playing arround in the DevOps and had to authorize again but I think it broke something. Now in the DevOps, I can see all the repos of the organization but not in the deployment center of my web apps where I only see 3, which are not the ones I want...
Since it's already authorized I can't see the "Authorize" button it asked the first time. I can "Change account" but it does nothing.
On Github I reinstalled Azure Pipelines in "Installed GitHub Apps" thinking it would fix the problem but it doesn't.
Azure App Service is also Approved in the "Third party access" tab. I tried to "Deny access/Grant access" whit no result.
Is there a way to remove the authorization on Azure and then re-authorize ? Or maybe I need to add something in the Github organization settings ?
Yes, this need you to re-authorization.
This is how to do that:
First, remove the old authorization.
Second, go to your web app and start a new authorization.
Third, The reason you ca n’t see it in the deployment is because you do n’t have access rights. You need to mark all the organizations that you need access to in this step.
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.
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.
When configuring continuous deployment in Team Project with http://portal.azure.com, I receive the following error:
Unable to locate blade 'ExistingWebsitesPickerBlade' in extension
definition. Search
path:'[0]WebsitesExtension-[1]ExistingWebsitesPickerBlade'.
Any ideas?
There is nothing wrong in the process of what you are doing, but this is indeed a bug where the new portal.azure.com fails to provide you the right blade containing your existing websites to configure continous deployment.
As you can see, this is a fairly regular error that others are experiencing throughout the whole portal experience.
http://devslice.net/2015/04/azure-app-service-orchestrating-business-processes/
There might also be an issue connected to which subscription level you are currently using (ex. BizSpark, Dreamspark, Pay-as-you.go etc.) which makes the portal fail in specific areas because of the former.
Provide adequate details for your subscription level to the Azure support team (create an incident), and they are your best bet at getting through with Continuous Deployment in the new Azure portal.