KME Support
My feedback
-
8,578 votes
if you have an existing post that you want to show in a different channel, you can edit the message and cross-post. This will add the top-level post to the different channel, but will not include the full set of replies. We will keep this request in mind as we evolve the cross-posting feature in the future and update if the status changes.
Details on cross posting can be found here: https://support.office.com/article/cross-post-a-channel-conversation-in-teams-9c1252a3-67ef-498e-a7c1-dd7147b3d295.
KME Support
supported this idea
·
-
4 votesKME Support
supported this idea
·
-
13 votes
An error occurred while saving the comment -
217 votesKME Support
supported this idea
·
-
539 votesKME Support
supported this idea
·
-
452 votes
Hey everyone — Suphatra’s back! And I’m on the case with this item.
I talked to engineering and I think they don’t understand this request. The requests says “Admin App” — do you mean Admin Center? The O365 portal?
Also, what exactly do you envision for central administration — for example — what can you do now, can’t do, and would like to do with this new feature.
Your feedback will help me get the team to put more resources into this. Thank you!
Suphatra
KME Support
supported this idea
·
If anyone has a problem deploying the bot in azure, with the error message:
{
"error": {
"code": "InvalidBotData",
"message": "Invalid Service Provider Id. "
}
}
following these Steps as a workaround has helped me:
--> delete the already created Resources or the Resourcegroup, if you created a new one for the moodle bot, to get a fresh deployment.
--> on the "custom deploymentpage", where you enter all the data to deploy the Teams Bot click "Edit template"
--> delete the following lines in the template:
--> on Line 108 delete: "serviceProviderDisplayName": "Azure Active Directory v2",
--> on Line 172 delete: "serviceProviderDisplayName": "[variables('serviceProviderDisplayName')]",
--> Click on save, to save the template
--> fill in all the required data and click on "purchase" to start the deployment once again
--> the deployment should be successful now!
If this comment is unsuitable here, please put it on the right spot and fix the bot template in azure so other people don't have to spend some hours debugging, like i had to ;-).
Thanks a lot!