This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 69%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMK%3C/text%3E%3C/svg%3E)
I'm removing this code as the ticket is not being addressed.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 10%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
Hi Michael - Thanks for raising the query.
We will look into it and let you know the updates.
Update: Could please make sure that the token used for authorization is valid and has not expired. Also, verify that the scopes and permissions required by your bot are correctly configured. Please verify and let us know if you're still facing the issue. So that, we will look into it and let you know the updates.
I'm removing this code as the ticket is not being addressed.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Hi @Michael Karampalas,
Sorry for the delay in the response. We are facing technical issue, and we are checking this internally. We will look into it and let you know the updates.
Hi Michael Karampalas,
We tried repro the issue. we see "Member not found in the conversion" even if we add one to one chat, or team.
Could you please refer this document https://learn.microsoft.com/en-us/microsoftteams/platform/resources/bot-v3/bot-conversations/bots-conv-proactive?tabs=csharp#proactively-install-your-app-using-graph. If possible, could you please send me exact repro steps. So, we will look into it and let you know the updates.
Using https://login.microsoftonline.com/botframework.com/oauth2/v2.0/token link with Post method with below mentioned key and values in the image attached. It will generate the access token.
Then setup any bot sample. Here, we setup https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-all-cards/csharp. Then, add your bot to the Teams. When sending a 'hi' message to the bot/ after adding bot app to the Teams. Apply the breakpoint 'OnMessageActivityAsync' function, the values you get there, update them in new api as per the below image and document https://learn.microsoft.com/en-us/microsoftteams/platform/resources/bot-v3/bot-conversations/bots-conv-proactive?tabs=csharp#examples.
Here, it will generate the 'Id value'. Update the generated 'Id value' in the link https://smba.trafficmanager.net/apac/v3/conversations/<id value>/activities as mentioned in the document https://learn.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-connector-send-and-receive-messages?view=azure-bot-service-4.0#send-a-non-reply-message. Then, update the values from 'OnMessageActivityAsync' function bot id and recipient id as like mentioned in the below image.
Finally, when you run this, you will be able to see the message from bot as per your code as like below mentioned image.
I'm removing this code as the ticket is not being addressed.
I have just fixed a mistake in the bot-token retrieval request. I don't think this is a good way to do this (huge support comments). I have this set up in Postman with a successful flow using a published bot, and an unsuccessful flow using the unpublished bot. Can I set up a call with the right dev? Alternatively, if you share an email, I can invite you to the postman instance.
Hi Michael Karampalas,
Sorry for the delay in the response. Could you please share your relevant information along with the code to microsoftteamsdev@microsoft.com. And we can have a further discussion and connect if needed.