You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I want to develop a bot that also runs in M365 Application. Right now I can config the Azure Bot Service via Portal to include M365Extensions channel as well, but it's not possible to do this via Bicep.
Confirmed that Bicep does not have M365Extensions channel available.
Considering that it is available in the REST API spec swagger, it may be that we're not generating the types correctly. @jeskew and @anthony-c-martin do you think you can check whether our types generation is working correctly?
The changes have only just been merged into the public specs repo (Azure/azure-rest-api-specs#22077), so I expect this'll be picked up by the next release of Bicep once type generation runs again - I have no reason to suspect a problem with our type generation.
Is your feature request related to a problem? Please describe.
I want to develop a bot that also runs in M365 Application. Right now I can config the Azure Bot Service via Portal to include M365Extensions channel as well, but it's not possible to do this via Bicep.
Describe the solution you'd like
Earlier the similar work was done for Outlook channel via this request : #5085
Can we have the similar work done for M365Extensions channel. This channel is now available in new swagger file of Azure Bot Service : https://github.com/Azure/azure-rest-api-specs/blob/main/specification/botservice/resource-manager/Microsoft.BotService/preview/2022-06-15-preview/botservice.json#L2822
The text was updated successfully, but these errors were encountered: