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.
Related
Am trying to help a customer move their services from an Azure Direct subscription to a CSP subscription. In the guides I've found, the approach used for IaaS1 (the old/class Azure - ASM) differ from what's used if a client's services all belong to IaaS2 (the new portal - ARM).
My confusion arises from the fact that while things like Class VMs can be easily identified if one views a client's services under the new portal - they are annotated as "Classic", am not so sure about any other services originally created under the ASM model.
And to further complicate things, it seems as though, viewing a client's services in the classic portal shows both ASM and ARM services, and this, without any means of distinguishing between them!
So, how do I go about this?
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.
Scenario:
One team had built one application, and application is running on azure.
maintenance is taken care by same team, we don't want to give full access of production instance to developer team, but want to give read permission, like - monitoring of logs, cpu usages etc.
Solution according to me is build an application which will get dashboard data and log data from azure via api and that data will be displayed to development team.
I am referring these 2 links
https://msdn.microsoft.com/en-us/library/azure/dn722415.aspx
https://azure.microsoft.com/en-in/documentation/articles/api-management-get-started/
Question:
Still I am not able to find api which will give the dashboard data. if anyone know api for the same, please help.
Is there any alternative solution for this scenario.
If you deploy your app using the new Azure Resource Manager mode, it provides a Role Based Access Control to your resources. You can deploy your app inside a Resource Group and provide read access to your developers. They will be able to view the information about the services that your app are made of but without the option to change anything.
This session from Build 2015 can help you to understand what ARM is and what you can do with it: https://channel9.msdn.com/Events/Build/2015/2-659
I created a Biztalk service (xyz.biztalk.windows.net) as a part of testing hybrid connection for my azure website.
I deleted the biztalk service (xyz) and tried to create a new service with the same name (xyz.biztalk.windows.net).
Azure would not allow me to use the same name (xyz). It gives me this error "the specified name is already in use or is not allowed"
Is there any specific time I need to wait until I can use the service name I deleted?
Any help or information related to this would greatly be appreciated.
According to my experiences with the Azure BizTalk Services Free and Developer tiers, I can only confirm this situation. This is not documented on MSDN as far as I was able to find out.
If this is a URL you where planning to use for a production environment, I suggest you contact Microsoft support.
I'm trying to use Set up deployment from source control to allow publishing from my TFS project to Azure, but for some reason after I authorize, it says I have no projects. The accounts are correct, I was just wondering, is there some kind of criteria for it to allow the integration or something?
I get this window
Yet I have two projects on my TFS Account.
Ended up closing my azure account and getting off of team foundation service, that solved the problem.