I created a bot via botframework.com. I no longer needed it and deleted it, also via botframework.com. It now still shows up in the Azure portal, but I'm unable to view it's details to delete it. (The bot in question is circled red in the screenshot).
I'm assume this is because it doesn't really exist anymore.
Below are attached Screenshots of my botframework view and my azure portal. I've censored some identifying information.
You can use the Azure CLI:
az resource delete --ids /subscriptions/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/resourceGroups/myresourcegroup/providers/Microsoft.Web/sites/mybot
This is the answer I received from the Azure Support Team, which worked for me:
• Open Azure PowerShell, and run the following command. In case you have not configured Azure PowerShell then you can follow the doc.
Login-AzureRmAccount
Select-AzureRmSubscription -SubscriptionId "<your subscription id>"
Remove-AzureRmWebApp -Name "<name of your bot>" -ResourceGroupName "<name of your resourcegroup>" -Force
Related
I'm trying to provision my bot to Azure but I'm getting the below error:
[Error] - code:Solution.ProvisionFailure, message: Failed to provision 'App Service plan'. Suggestions: Please check log in output channel and try to fix this issue.
No details in the output channel.
Any idea why that's happening? I just used the default project configuration, didn't change a thing.
Thanks
I am the developer of Teams Toolkit in Microsoft, thanks for trying our new Toolkit. According to this tutorial https://learn.microsoft.com/en-us/microsoftteams/platform/get-started/first-app-bot?tabs=vscode#deploy-your-app-to-azure, when you provision to Azure resource, have you been asked to login your Azure account by browser? Have you ever seen the confirm window that saying "The Teams Toolkit will provision resources under xxx (Azure account) with xxx (subscription)"? If yes, please check if the Azure account and subscription is correct.
One update is that in Teams Toolkit v2.2.0, we add one feature to provide more error details. If you upgrade the VSCode extension, you can check the OUTPUT channel (select "Teams Toolkit" channel) to see more details as below.
I know how to publish a serverless application using aws visual studio toolkit.
It's just you login into aws explorer with user's access key & Secret access key. and then right click on the solution and publish to AWS lambda. It's so simple.
But what about if i have my user has a different assume role that further has access to all the AWS resources and can publish.
So i know how to publish it using assume role via aws CLI by creating a profile let's say "powerdevrole" and whenever we type any command deploy then we use "--profile powerdevrole" in the end with MFA access enabled.
So my question is how to publish the same using aws toolkit if we have an assume role and MFA enabled on that??
Also i have tried to get the cached keys and then used that into aws explorer to publish my project but it's not working for me.
Please help me out.
Thanks,
Vinod Bhatt
I am having an issue after migrating my Bot to Azure. I have a Bot that is up and running on Cortana Chanel as well. I previously published it only for me ‘Deployed to self’ so I can see it on my Cortana Canvas but now I want to publish it for group of people but I am unable to do it from Azure portal. Whenever I click on ‘Edit’ button of Cortana Channel through Azure Portal following error prompts me:
As per the error they are expecting me to use my Microsoft Personal Account (i.e. Hotmail or Outlook Account) but unfortunately in my case it’s not possible. I have azure subscriptions in my office account not in my personal account that’s why I migrated all my bots to my office account and now trying to configure it for other peoples (i.e. Deployment for Group) but because of the above error I could not do it. As I know previously it was very straight forward all we have to go to ‘Cortana Dashboard’ and there is an option of deployment by which we can easily publish our skill sets to the group of people by just adding there email address.
Could you please help me how can I resolve this issue? All I want to use my azure account (i.e. my company account) to configure the Cortana channel and other things like Deployment to Group of peoples.
I'm trying to create a release definition in Visual Studio Online with the task "Deploy Azure App Service".
When I try to authorize for the subscriptions it gives this error message below.
Error(s):
Insufficient privileges to complete the operation. For troubleshooting refer to link.
The content of the link they provide doesn't seem to help me.
I already tried this using Azure Service Administrator account.
Why is this happening? What are the kind of permissions i need for doing this?
The user must be a member of Global Admin role in the directory.
On the other hand, you may configure it manually with this PowerShell script.
More information, you can refer to Automating Azure Resource Group deployment using a Service Principal in Visual Studio Online: Build/Release Management (Manual configuration section)
Download & run this PowerShell script in an Azure Powershell window to
generate required data for Service Principal based Azure service
connection. Running this script would prompt you for:
The name of your Azure Subscription name
A password that you would like to set for the Service Principal that is going to be created
Note: the script has been tested with Azure PowerShell version 1.0.2.
Once successful, the script would output the following details for the
Azure Service Endpoint.
Connection Name
Subscription Id
Subscription Name
Service Principal Client Id
Service Principal key
Tenant Id
I followed the steps as per
https://github.com/OfficeDev/O365-WebApp-MultiTenant and added the connected service. However this does not register the app under Windows Azure Active Directory Applications. I have properly linked my office 365 account into Azure. However when I add the connected service it is still empty. Is this a known issue and what is the work around?
No, this isn't a known issue. The "Add Connected Service" wizard is not generating a client ID and secret in your web.config?
As a workaround you could login to the Azure Management Portal and register the app manually, then put the client ID and secret into your web.config.
I just had the same issue and spend some hours on it. Finally it turns out that I had used a user account to log in in visual studio that was assigned to a different MS Azure account.
In my case I was using the user of production environment instead of my own developer account to log in.