I'm using azure free trial. I suspect that might be the issue, although couldn't find anything in the docs. When publishing from composer to azure there are resources that need to be added and then there are a few optional resources. In composer I checked all the resources - although prob don't need all of them.
Then hit the create button and it says "Provisioning..." and then the message came up:
{"name":"CREATE_COSMOSDB_ERROR","message":"Error - The subscription is not registered to use namespace 'Microsoft.DocumentDB'. See https://aka.ms/rps-not-found for how to register subscriptions.","stack":"Error\n at new CustomizeError (C:\Program Files\Bot Framework Composer\resources\app.asar.unpacked\extensions\azurePublish\dist\extension.js:276418:25)\n at createCustomizeError (C:\Program Files\Bot Framework Composer\resources\app.asar.unpacked\extensions\azurePublish\dist\extension.js:276423:10)\n at AzureResourceMananger.deployCosmosDBResource (C:\Program Files\Bot Framework Composer\resources\app.asar.unpacked\extensions\azurePublish\dist\extension.js:277631:13)"}.
In the azure activity log it looks like:
I was wondering if I have to upgrade in Azure to pay as you go?
And also what the minimum resource requirements to have a bot published to Azure.
Thx
Composer does not necessarily try to use the free tier offerings when publishing. You may have to instead create Azure resources manually and then create a publishing profile from existing resources.
Related
I want to publish an web application on Azure market place.
I can create a Linux VM, install Java, Tomcat, SQL server and create an image of it. But instead of that, is it possible to create a tomcat instance along with database on Azure portal, add it to a resource group and publish this resource group on market place?
Would this approach be more advantageous?
thanks
As per the doc here:
https://learn.microsoft.com/en-us/azure/marketplace-publishing/marketplace-publishing-getting-started
Azure Marketplace offerings are based on Azure VM images or solution templates, your current solution would be the VM based route. It sounds like you may want to look at the solution template route to leverage other capabilities such as Azure SQL Server.
Neither route enable "publish this resource group to the market place". If that is the route you are aiming for that is essentially building out a multi-tenant application which is a bigger task and perhaps something like this link will help get you started:
https://azure.microsoft.com/en-gb/blog/with-newly-available-services-azure-continues-to-be-the-best-place-for-software-as-a-service-developers/
There are also other stackoverflow answers which may be of help:
Does a developer have to pay for publishing a SaaS app on Windows Azure Marketplace?
How can i publish my web solution to Marketplace
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.
I wanted to create a "Redis Cloud" via the Azure marketplace but I didn't found this service in the marketplace list.
Doesn't it exist anymore? Why?
Or is there some kind of limitation, e.g. it's only available for certain types of Azure subscriptions?
I'm wondering because via redislabs.com I can still choose "Azure" for creating a Redis Cloud - but not via Azure marketplace.
Sadly, you are right Munchkin.
I've looked into the matter and it appears that our Redis Cloud plugin is stuck in limbo between the old and new portals. This is an Azure team issue and we're waiting for a resolution from them.
Until this is rectified, note that you can always create a direct subscription via our website however and do feel free to contact our support team with any questions.
You can find it in the "New Portal" Azure Marketplace, http://portal.azure.com. There you should be able to find it listed as "Redis Cache" or Redis Cloud, first one is Managed by Microsoft, the second one is IaaS on a VM.
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.
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.