-
Notifications
You must be signed in to change notification settings - Fork 756
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config Outlook as a Channel for Bot Service #5085
Comments
My guess is the channelName name property is missing this allowed value, but it should still be possible to use that value if we can figure out what it is. I created one quickly, and from resources.azure.com, it looks like it is simply called So if you specify |
Hi, kindly follow up on this - is there any update on this issue? Thanks! |
Did you try using I'm not sure when the type information will get updated for this as it is dependent on the RP team providing it, but it should not block you from making progress. |
Yes, the bot service team needs to update their REST API spec to include this enum value for this property. |
we have alread created a pull request |
Closing this issue. We will track the |
Hey @alex-frankel , I see Azure/azure-rest-api-specs#18149 has been merged, would bicep be automatically updated if so, which version should I use? I have tried |
Interesting - I don't see this channel either on Bicep v0.5.6 and our most recent release was 12 days ago and this swagger change was checked in 14 days ago. It is possible we just missed it and generated the types a few days before our release and before this got merged. @shenglol / @majastrz -- does that sound right? If so, then this will get picked up when we release Bicep v0.6 at the end of the month. Repro: resource botParent 'Microsoft.BotService/botServices@2021-05-01-preview' = {
name: 'foo'
resource bot 'channels' = {
name: // open completions here
}
} |
That's right. The types were generated before the rest API spec PR got merged. |
Thanks for the response @alex-frankel and @shenglol , seems like I can expect an updated on Bicep by end of April to pick up the latest swagger change from Bot Service? |
Yes. |
Is your feature request related to a problem? Please describe.
I want to develop a bot that also runs in the Outlook, right I can config the Azure Bot Service via Portal to include Outlook as well, but it's not possible to do this via Bicep. (Which my Bot Service and Configuration is provisioned using Bicep)
Describe the solution you'd like
I would like to config my bot service with outlook as an channel in similar way to config Teams.
The text was updated successfully, but these errors were encountered: