I have TodoSkill deployed in Azure. Then, had to integrate the skill to virtual assistant app. It failed in AAD integration part.
PS E:\BotSamples\virtual-assistant\cs\MyAssistant1\MyAssistant1\MyAssistant1> botskills connect --botName myassistant1-lu7hdxd --remoteManifest "https://todoskill1-4khiws3.azurewebsites.net/api/skill/manifest" --luisFolder "E:\BotSamples\virtual-assistant\cs\TodoSkill1\todoskill\Deployment\Resources\LU\en\" --cs
..
..
Please review your updated dispatch model in E:\BotSamples\virtual-assistant\cs\MyAssistant1\MyAssistant1\MyAssistant1\Deployment\Resources\Dispatch\en\Summary.html
Running LuisGen...
Executing luisgen for the myassistant1en_Dispatch file
Successfully refreshed Dispatch model
You need to re-publish your Virtual Assistant in order to have these changes available for Azure based testing
Appending 'ToDo Skill' manifest to your assistant's skills configuration file.
Successfully appended 'ToDo Skill' manifest to your assistant's skills configuration file!
Configuring bot auth settings
Checking for authentication settings ...
Configuring Azure AD connection ...
Checking for existing aad connections
Could not configure authentication connection automatically.
There was an error while executing the following command:
az bot authsetting list -n myassistant1-lu7hdxd -g myassistant1-lu7hdxd${err}
You must configure one of the following connection types MANUALLY in the Azure Portal:
Azure Active Directory v2
For more information on setting up the authentication configuration manually go to:
https://github.com/microsoft/botframework-solutions/blob/master/docs/howto/assistant/linkedaccounts.md#authentication-configuration
The link seems to be old.
I'm taking a look at this now. At this point I don't know any of those answers off the top of my head.
Either you could try to repro on your end, or I can show the problem at my end. I have a bit of urgency. If you could confirm on the next steps, it would be great.
@PurnaChandraPanda did you try manually add the "Azure Active Directory v2" connect setting?
No, I did not try any manual entry for AAD v2. Could you please help me where it should be done (todoskill or virtual assistant level)?
Hi,
Open your Web App Bot in Azure
-> settings
In 'Oauth Connection Settings'
-> Add seeting

This Name property should correspond with what your config in appsetting.json:
"oauthConnections": [
{
"name": "Outlook",
"provider": "Azure Active Directory v2"
}
When going for new setting under "OAuth Connection Settings" and aad v2 provider is being picked, it asks for client ID. So, created a new app registration with appserviceuri/signin-oidc. However, I am not clear what permission that i should pick here. Can you please help?
For the scopes, you can see this doc:
https://github.com/microsoft/botframework-solutions/blob/master/docs/reference/skills/productivity-todo.md#authentication-connection-settings
The link resulted in 404 - not found!
We published a new documentation site yesterday, here is the updated link: https://microsoft.github.io/botframework-solutions/reference/skills/productivity-todo/
Also the link to the guide on manually setting auth is here: https://aka.ms/vamanualauthsteps (the CLI tool link has been updated)
Here is what I tried to integrate TodoSkill with virtual assistant bot:
"oauthConnections": [
{
"name": "Outlook",
"provider": "Azure Active Directory v2"
}
],
any comments on my above comment?
When you invoke skill from VA, it is unnecessary to set oauthConnections for skill.
Work accounts from Microsoft are not allowed.. Use this instead https://cdx.transform.microsoft.com/my-tenants
@PurnaChandraPanda Were you using a Microsoft.com account to authenticate? If so, as per xieofxie this not allowed as per policy. You can use a custom o365 tenant or a personal MSA. Let us know.
All Apps at Microsoft require admin consent for graph scopes.
Yes, I was using microsoft.com account to authenticate. By following the link with my email id, created a custom tenant. I think next task would be to associate an Azure subscription. How is it done?
You should be able to just login using credentials from your tenant.
Closed - original issue was that link provided in the botskills output to manually setup auth connection wasn't followed. Have followed up to try and see if we can provide more guidance as to why the configuration cannot be done automatically - typically security restrictions on a tenant.
Also moved to an aka.ms link in botskills (if you update botskills you'll see this)
@PurnaChandraPanda if you have time it would be really helpful if you updated botskills npm update -g botskills and re-ran it - it should now give you a full error message to explain the root cause on why you had to do it manually.
Alternatively you can just run this
az bot authsetting list -n myassistant1-lu7hdxd -g myassistant1-lu7hdxd