I created one Azure bot service and I am unable to find the password for the bot created. I want to integrate the Dialogflow with Teams bot. As part of the process I created Azurebot but I needed password and ID of which I got ID but password is nowhere is seen. Searched a lot on the net but couldnt find solution.
Azure bot service and I am unable to find the password
Usually, the Bot secret and file are store in application settings in the app service and AppID and Password are securely encrypted in .bot file.
As per my analysis on referring to #The Bot Framework Team. refer this article.
Steps to find password with reference of above article
In the Azure Portal, select your bot’s Resource Group
Select Deployments in the blade to the right
In the blade which opens, select your Bot under Deployment Name. This will open up a new blade overview for your bot deployment.
Select Inputs - > Here, you can find a lot of meta data for your Bot, including your Bot’s AppID and Password!
Sceanrio2:
Another way to find App Registration password.
there is another way,
Goto App Registrations -> search with APPId -> Go to Certificates & Secrets -> there we can find the password.
NOTE: If it not visible create a new and use that into the integration.
Related
I want to deploy my bot using this instruction https://learn.microsoft.com/en-us/azure/bot-service/bot-builder-tutorial-deploy-basic-bot?view=azure-bot-service-4.0&tabs = csharp, but on the third point I have a problem.
I am running the command "az ad app create --display-name" displayName "--password" AtLeastSixteenCharacters_0 "--available-to-other-tenants".
In place of "displayName" I insert the name of the bot, and on "AtLeastSixteenCharacters_0" I enter a random password, but I get the answer "Found an existing application instance of" ******************** ** ". We will patch it
Updates to converged applications are not allowed in this version ".
If the password field is left blank, the operation will be successful, but how can I get this password?
In the Azure portal, on the bot tab in the Configuration section, the Microsoft App ID (Manage) field displays the id and the tooltip says that "You can generate a new password by clicking on the 'Manage' link." is a No access 403 error.
How can I get this password
Solution 1: An Azure Bot resource has an application ID (app ID) and a password associated with it. The Azure Bot Service assigns a unique application ID to the application. You can obtain the password following the steps described below.
1) In your browser, navigate to the Azure portal.
2) In the resource list, click on the registration application name.
3) In the right panel go to the Bot Management section and click Settings. The registration application Settings page will display.
4) Select the Manage link next to Microsoft App ID.
5) In the Certificates & secrets pane, click the New client secret button.
6) Add the description, select the expiration time, and click the Add button.
This will generate a new password for your bot. Copy this password and save it to a file. This is the only time you will see this password. If you do not have the full password saved, you will need to repeat the process to create a new password should you need it later.
For more details refer this document
Solution 2: Use the latest version of the Azure CLI. If you are using an Azure CLI version older than 2.2.0, you might encounter errors.
1) Login to azure portal
az login
Note: If you deploy your bot to a non-Azure cloud such as US Gov, you need to run az cloud set --name before az login, where is the name of a registered cloud, such as AzureUSGovernment. If you want to go back to public cloud, you can run az cloud set --name AzureCloud.
2) Set the default subscription to use.
az account set --subscription "<azure-subscription-id>"
3) create an Azure application registration
az ad app create --display-name "displayName" --password "AtLeastSixteenCharacters_0" --available-to-other-tenants
display-name :The display name of the application. It is listed in the Azure portal in the general resources list and in the resource group it belongs.
Password :The password, also known as client secret, for the application. This is a password you create for this resource. It must be at least 16 characters long, contain at least 1 upper or lower case alphabetical character, and contain at least 1 special character.
available-to-other-tenants : Indicates that the application can be used from any Azure AD tenant. Set this to enable your bot to work with the Azure Bot Service channels
For more details refer this document.
I'm trying to use Video Indexer API (v2). But when I try to sign in to it using the the Azure Active Directory, I get this message:
Selected user account does not exist in tenant 'Microsoft' and cannot access the application 'da0eb6e2-d2bd-4cbd-ad65-81ddc43546e2' in that tenant. The account needs to be added as an external user in the tenant first. Please use a different account.
I'm not sure what the issue is?
Sign-in to the VideoIndexer developer portal has been revised.
We unified the developer portal sign-in with that of the VideoIndexer site.
The screenshot in #Mohit_Garg comment in no longer relevant. This is our new sign-in experience.
The first option should be used in case of Active Directory accounts. This is also the only option that will allow you to use Video Indexer paid.
In many cases users selected the Microsoft option in the old authentication method when they actually wanted AAD option.
After the new experience they select the first option "Sign in with a corporate account" and get a message saying that an account with that E-Mail already exit.
An Email is unique in Video Indexer developer portal. So if you want to use your AAD but previously opened an account in the developer portal using a different authentication method you will need to sign-in using the original authentication method and close the account in your developer profile page. After the account removal you will be able to sign in with different authentication method.
More info can be found in the official video indexer documentation
Clarification: I'm a developer in the Video Indexer team.
Follow below steps to Subscribe to the API -
Sign in.
To start developing with Video Indexer, you must first Sign In to the Video Indexer portal.
If signing in with an AAD account (for example, alice#contoso.onmicrosoft.com) you must go through two preliminary steps:
A. Contact us at visupport#microsoft.com to register your AAD organization’s domain (contoso.onmicrosoft.com).
B. Your AAD organization’s admin must first sign in to grant the portal permissions to your org. To do this, the organization's admin must navigate to https://videobreakdown.portal.azure-api.net/signin-callback?provider=Aad, sign in and give consent.
Subscribe.
Select the Products tab. Then, select Production and subscribe.
Once you subscribe, you will be able to see your subscription and your primary and secondary keys. The keys should be protected. The keys should only be used by your server code. They should not be available on the client side (.js, .html, etc.).
Start developing.
You are ready to start integrating with the API. Find the detailed description of each Video Indexer REST API.
I'm trying to create a simple chat bot on Microsoft Bot Framework and I want to add LUIS app ID and LUIS subscription key to my application.
Where can I get the subscription key?
I believe lately Microsoft has changed the structure of the portal so most of the links are not working.
Where can I get the subscription key?
You can get the subscription key by going to
The "Publish App" link on the left,
Select staging from the "end point slot" under Publish Settings. (Don't know why doesn't it show while the option is Production. Maybe there are other ways to connect in the production environment)
Selecting the "staging" option will show an endpoint url which will have "subscription-key" field, which you can copy
I want to add LUIS app ID
To get your luis app ID
Go to "My Apps" in "https://www.luis.ai/applications"
Click your app
Click settings from the options on the left
Copy the 36 character "Application Id"
The followings are steps that worked for me:
Login into https://portal.azure.com
Search luis
Create 1 Language understanding in Cognitive Service section
Go to "My Apps" in https://www.luis.ai/applications
Select your app
Click on Change link nearing Assigned endpoint key
Select available items in 3 comboboxes
Here is the result that you could get subscription key
Hope this help.
Subscription key: In azure create a new cognitive service -> Luis. In the new luis service, on the left you can find an option labeled keys. Use Key1 for everything.
API key: go to your luis.ai account, and select the key's tab. You need to link your luis subscription key here to link luis to your azure sub.
You can navigate at this page https://www.luis.ai/keys where you will see "Programmatic API Key" it's your subscription key also known as "Ocp-Apim-Subscription-Key".
I found this article on msdn that really explains the keys well https://blogs.msdn.microsoft.com/kwill/2017/05/17/http-401-access-denied-when-calling-azure-cognitive-services-apis/
you can find your subscription keys the azure portal
Location of Subscription Key for Luis Services
the application id can be found on the settings page of your app on the luis dashboard (start at www.luis.ai)
... all the details for this are in the article linked, but what I found was that:
Use the key as in the screenshot above
The region your azure resource for luis is in, should match the region that your luis application is in.
The resource is managed through the azure portal, the luis app is managed through the www.luis.ai homepage
As the article says, it can be quite confusing about what keys to use where, (especially when you first create the luis app you get a 'starter key' ... sorry for the waffle,
The Subscription Key is the same as the Authoring Key (refer to this documentation). You can get the Authoring Key for your LUIS app by taking the following steps:
Log on to luis.ai
Navigate to the MANAGE menu
Navigate to the Keys and Endpoints tab on the sidebar
I am new to Azure. I am getting myself confused very fast. My company has a project on Azure. We are looking to grant access to our external developers so they can log into our account and build a product for us ( setup a VM with mysql dbs and build an application ).
The only options I see are to invite users from another Active Directory or users who are in my own Active Directory? Is there no option to simply create a sign in credential for a user with say " email at gmail dot com" ?
What am I missing? I have created a Resource group but still can't invite anyone of our external consultants in there.
You can invite any user to manage your resources or your subscription.
There are 3 conditions for it:
You have the right to add it to your Azure AD
you are the owner of the subscription
The 'Guest user' already has an Azure account or a Microsoft Account
Then you have to go to:
Resources/Subscriptions
Access Control
Select a role (i.e. Contributor)
Type in the Account/Email of your external team member
check the checkbox and send the invitation
If you want to create generic users you can go straight forward to your AD and create a user i.e. developer1#contoso.onmicrosoft.com and add this user to the resource/subscription. Don't forget to take note of the credentials you created
So you would use Azure RBAC for that. Just click on the Resource Group > Access Control > Add.
You could also consult this blogpost for best practises.
If you just need them to develop and access SQL or a web App, you can pass the publish profile and SQL connection string to them.
Also, you can setup continous integration for the web App or virtual machine and pass git or GitHub or whatever source control you are using and pass the URL for the project, then they will commit the source code and fire a new build
Trying to play with the newly announced service, but am having problems getting started.
Entered name, subscription, etc.
Got my Microsoft App ID, entered it into the form
Selected C#
Selected any one of the templates
When I click Create Bot I get "This MSA App ID is already in use"
What do I need to do?
I clicked the Manage and created a set (app id / password) and used that instead of the previous values and it worked ok thereafter.
Background to my answer: For some reason, my current Bot Service stopped working and I had to create a new Bot Service to provide the back-end for my already published bot. However, when you try to create a new Bot Service using your already published bot App ID and App secret, you will get the same message ("This MSA App ID is already in use").
Solution: Delete the old Bot service that does not work anymore. Then create a new Bot Service (with new App ID and App secret) with the same name as your old Bot Service name (so the messaging endpoint URL will look similar). This process will create a new bot in your bot framework portal (under My bots). Now you need to do two things:
Go to your newly created Bot Service (In Azure portal), find the application settings under "settings" tab. In application settings, replace the MicrosoftAppId and MicrosoftAppPassword with the AppId and App secret (= app password) from your published bot. You can find the App ID and password of your published bot from the Bot Framework portal.
In the Bot Framework portal, find your newly created bot under "My bots". You need to copy the messaging endpoint of this bot, into your messaging endpoint of your old (published) bot. In the portal, click on "Edit" besides the "Details" section. Scroll down and copy the messaging endpoint. Go to "My bots" again and click on your old bot. Click the "Edit" besides the "Details" section and paste the endpoint URL there.
Now your newly created bot service (Azure portal) is connected to your old published bot (in Bot Framework Portal). You can go ahead and delete the newly created bot in your Bot Framework portal, as you do not need it anymore.
Most likely you already registered a Microsoft Application with that ID. You need to create a new App Registration and use that one: https://apps.dev.microsoft.com/#/appList