Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Actions][Docs] Modify connector documentation with the new MS Exchange online configuration requirements #111449

Closed
YulNaumenko opened this issue Sep 7, 2021 · 1 comment · Fixed by #112768
Closed

[Actions][Docs] Modify connector documentation with the new MS Exchange online configuration requirements #111449

YulNaumenko opened this issue Sep 7, 2021 · 1 comment · Fixed by #112768
Assignees
@YulNaumenko
Labels
docs estimate:small Small Estimated Level of Effort Feature:Actions/Framework Issues related to the Actions Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@YulNaumenko
Copy link
Contributor

  1. Based on the changes done in the [Actions][Connectors] Change email connector API for MS Exchange Online provider by replacing Basic Auth with OAuth 2.0 Client Credentials flow #111439 and [Actions][Connectors] Modify email connector UI flyout to support OAuth 2.0 Client Credentials flow for MS Exchange provider #111443 we need to update existing documentation with the information how to configure OAuth 2.0 Client Credentials flow and how to grant the administrator consent for the Graph API permissions for Kibana integration application.

Screen Shot 2021-09-07 at 11 19 21 AM

What should be important to cover in the docs:
  • how to create Elastic Kibana application in Microsoft admin portal
  • which permissions should be required as minimum to start Kibana actions sending emails
  • required administrator consent on the given minimum permissions
  • where to get client ID, client Secret and tenant ID
  1. UI should be extended with proper doc links if user need a help.
@YulNaumenko YulNaumenko added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) docs Feature:Actions/Framework Issues related to the Actions Framework labels Sep 7, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@YulNaumenko YulNaumenko added the estimate:small Small Estimated Level of Effort label Sep 7, 2021
This was referenced Sep 11, 2021
Closed
Open
@YulNaumenko YulNaumenko self-assigned this Sep 20, 2021
This was referenced Sep 22, 2021
Merged
Merged
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@YulNaumenko YulNaumenko

Labels
docs estimate:small Small Estimated Level of Effort Feature:Actions/Framework Issues related to the Actions Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
3 participants
@kobelb @elasticmachine @YulNaumenko