The screen is stuck with the "Create Blade" message.
Tried both on Chrome and Edge
I don't know why is this happening to you. It's working fine for me.
If you still not able to make it work. Make sure you have enough amount in your Azure subscription (or) your subscription is Active.
However Azure Portal is a simple GUI to create any resources easily. But it doesn't mean to stop you from using other ways like Azure CLI, Powershell, ARM templates, Other SDK's
Azure CLI to create a WebApp Bot
Dot Net SDK to create a WebApp Bot
Node.js SDK to create a webApp Bot
Related
I'm trying to find a way to get dotnet-counters output from Azure App Services to either the Azure Portal (good enough for some trouble shooting) or some other console tool.
Does anyone know of a way to get the data, even when the app service is running across multiple app service plans? I was picturing maybe there is an app service extension (but no luck so far).
Eventually I'll want to automate this so I can get the data onto our monitoring system, but first baby steps.... just need something I can manually eyeball to help debug issues.
Anyone have any thoughts on how to do this?
Thanks
Ken
From offical doc, we can install dotnet-counters by cli command and download .exe directly.
As azure web app running in sandbox environment, so we can't add dotnet-counters to env, which means we can install it, but we can't use it.
So my solution is,
we can download .exe file directly.
After downloading finished, we can copy and paste it to wwwroot.
Then we can use it on scm site and azure portal.
On kudu site.
On azure portal.
So I am using Azure Functions at work and thought I would have a play and install them on my own server. I have successfully installed Azure Functions Runtime 2 (preview).
I have then followed the Java tutorial to create an Azure Function :
https://learn.microsoft.com/en-us/azure/azure-functions/functions-create-first-java-maven
How do I then deploy this function to my own Azure functions server?
In the guide it says about using :
az login
mvn azure-functions:deploy
Unfortunately, mvn azure-functions:deploy is to deploy functions to Azure site as az login is required before deployment, which doesn't support deployment to on-premises Runtime portal.
But the key point is, the on-premises Runtime is obsolete(one year behind the latest bits), new project probably can't work with it even if we find how to publish.
Since v2 becomes GA, it is recommended to leverage custom image for usages out of Azure box.
Update
Missed one point. As AF Team answered in the issue you post, no Java Image for now so the usage of Azure Java Function outside Azure is blocked unless we could figure out creating the image on our own.
I am trying to deploy the basic-bot Microsoft Botbuilder sample application to azure.
I started by creating a new botbuilder node.js sample application through the Azure dashboard, and I was able to successfully follow the instructions here to download and redeploy the application.
I then attempted to copy over the deploy scripts and .env file from the downloaded sample application into the basic-bot application, and attempted to publish using the az bot publish command from the link above. This successfully deployed the basic-bot application, but the deployed application now returns 500 errors. Initially, the 500 errors were caused by the "botbuilder-ai" nodejs package not being installed. I installed this package manually through the Azure console, and this error went away. But the application continues throw 500 errors, without producing a stack trace, and I have not been able to determine why.
The only official documentation I have found that explains how to deploy the bot is specifically for C# and Visual Studio. Is there a way to deploy a bot to azure for a Node.js app using the azure CLI?
Thank you.
Is there a way to deploy a bot to azure for a Node.js app using the
azure CLI?
Yes there is. You can type az bot publish -h for all the options available to you when publishing a bot. Here are some tips about getting it to work:
You will need to log in to Azure with az login
Make sure you've set an active subscription. Type az account set -h for help. Use az account list to see your choices of subscriptions and az account show to see the current active subscription
Publishing can be easier if you set the resource group you're publishing to as your default. Unlike your active subscription, configured defaults don't reset when you log out. Use az configure to see your current defaults and az configure -h to see how to set a default resource group
If you publish and it says Not a valid azure publish directory. missing post deploy scripts then you'll need a PostDeployScripts folder in your bot folder
There are some instructions in the deploymentScripts folder that you might find helpful. Note that as an alternative to the Azure CLI, you can also publish from Visual Studio Code using the Azure App Service extension.
If you publish successfully and you're getting errors when you try to test in Web Chat, sometimes Azure needs a little nudging. When I checked my Channels blade it said Web Chat was encountering errors regarding missing files. I tried some troubleshooting steps and eventually got it to work without any real changes.
Try logging out of your Azure account in the online portal and then logging back in
Try running your code in the online code editor in the Build blade
Try publishing again
Regarding your specific situation of trying to repurpose the downloaded source code to deploy the basic-bot sample, there are a few things you need to know. The .bot file is very important as it contains information about all the services the bot uses, but basic-bot.bot contains none of the needed information. In addition to the deployment scripts and the .env file you will also need to copy over your .bot file. However, basic-bot's bot.js expects the .bot file to contain a LUIS service named "basic-bot-LUIS" so you need to go into the bot.js code and change the value of LUIS_CONFIGURATION to the name of the LUIS service in your .bot file ("BasicBotLuisApplication" if you downloaded the V4 Basic Bot NodeJS code and kept it the same). Make sure you can get the basic-bot sample to run locally before you try to publish it.
I have setup Sitecore 8.2 Update 3 as Azure App Service using Marketplace.
The setup completed and i got urls for cm and cd like
xxxxxx-cd.azurewebsites.net and
xxxxxx-cm.azurewebsites.net
But when I access these URLs I get this screen.
Also xxxxxx-cm.azurewebsites.net/sitecore gives page not found.
Am I missing anything?
According to your screen, the Azure App Service has been created, but there is nothing inside it. Seem like something went wrong and deployment script didn't deploy Sitecore's file to App Service. You can verify it using App Service Editor tool.
The reason why deployment went wrong could be this known issue: https://kb.sitecore.net/articles/755670.
I've setup a continuous deployment between Bitbucket and the new Azure portal (preview). It works great but when I checked Bitbucket, I noticed that it created a services rather than a webhook but in the service section and the following message is displayed:
In the future, you will not be able to create POST or Pull Request POST services from this screen, as Bitbucket's new and improved webhooks will replace these services. Existing POST services will continue to function as expected for now. To create a new webhook, refer to the documentation for Bitbucket's updated webhooks.
But I can't figure out how to create a webhook in the new Azure Portal. Every articles on the web that I have found are all explaining it based on the old ('current') portal.
Any ideas on how I can create a webhook instead? Not critical since it's working but considering the message displayed in Bitbucket, I thought I'd look into it now rather than wait for bitbucket to disable this feature.
Thanks.
Login to Old Azure Console, https://manage.windowsazure.com
Goto Configure
Find out DEPLOYMENT TRIGGER URL
You can use this trigger URL to setup webhook in BitBucket
But I don't think you have to worry much as Azure will automatically upgrade their services to do this automatically, that is what managed cloud means, we are paying them to manage this.