Hi! Is it possible to reply on Teams and reflect that answer on Discourse?
1개의 좋아요
It’s not - this integration is just one-way from Discourse → Teams
1개의 좋아요
Hi @david ,
Will this change affect the plugin/guide? Retirement of Office 365 Connectors within Microsoft Teams
2개의 좋아요
It looks like it will, yes. @crossheadscrewdriver has a work-in-progress which will add support for Power Automate instead.
2개의 좋아요
@danilofmesquita, yes the retirement of the O365 connector was the main driver for me to build support for Power Automate as an integration. I will attempt to spend some time on my PR this weekend so it can be merged next week ( fingers crossed 
)
I’ll also attempt to create both a guide to create a new chat integration with Power Automate and to migrate existing chat integrations to Power Automate.
4개의 좋아요
Support for Power Automate as a provider just got merged (thank you again @david for the quick turnaround).
I am having issues now creating the guides for the integration as it seems I am not allowed to create new topics in the Documentation category and I don’t see one being created automatically.
Do I need to make a request somewhere?
3개의 좋아요
Contribute > Feature 같은 곳에 토픽을 만든 뒤, 이곳으로 이동해 달라고 요청하는 것이 가장 좋다고 생각합니다.
(cc @JammyDodger - 제가 틀렸다면 지적해 주세요)
2개의 좋아요
Currently, you need to be TL2 to create and edit Documentation topics. It looks like you’re a couple of visits and handing out a heart away. For simplicity, let’s bump you up now and then you should be able to create that topic. 
4개의 좋아요
This appears to use unauthenticated webhooks into teams, which for our organisation would rule this integration out on security grounds.
Is there a way to support Service Principle auth or user auth? Service principle would probably the most preferred for most large organisations.
Enabling this auth would mitigate against any future M365 exploit via webhooks (unless the attacker gets hold of a key)