O365 | Add permissions to docs

[kcreddy]

Proposed commit message

The setup and permissions required were missing and/or too vague for the users to follow. So update the integration docs to reflect O365 Management API permissions that are required to consume audit logs.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-11-16T07:56:02.201+0000

• Duration: 17 min 21 sec

Test stats 🧪

Test	Results
Failed	0
Passed	25
Skipped	0
Total	25

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (1/1)	💚
Classes	100.0% (1/1)	💚
Methods	100.0% (16/16)	💚 2.469
Lines	81.579% (744/912)	👎 -0.814
Conditionals	100.0% (0/0)	💚

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[efd6]

Suggested commit message:

The setup and permissions required were missing and/or too vague for the users
to follow. So update the integration docs to reflect O365 Management API
permissions that are required to consume audit logs.

(the WHAT and WHY were intended to be directives to the commit message author not to be included in the commit message).

Change looks good for language. Deferring to people with expertise in the configuration.

[elasticmachine]

Package o365 - 1.29.1 containing this change is available at https://epr.elastic.co/search?package=o365