Skip to content

microsoft_exchange_online_message_trace: document service principal provisioning step#18240

Merged
chemamartinez merged 2 commits intoelastic:mainfrom
chemamartinez:microsoft_exchange_online_message_trace-improve-provisioning-steps
Apr 7, 2026
Merged

microsoft_exchange_online_message_trace: document service principal provisioning step#18240
chemamartinez merged 2 commits intoelastic:mainfrom
chemamartinez:microsoft_exchange_online_message_trace-improve-provisioning-steps

Conversation

@chemamartinez
Copy link
Copy Markdown
Contributor

Proposed commit message

microsoft_exchange_online_message_trace: document service principal provisioning step

Add the Microsoft-owned App ID (8bd644d1-64a1-4d4b-ae52-2e0cbf64e373)
and the PowerShell commands needed to provision its service principal in
the tenant. Without this step, the Graph API returns a 401 referencing
that App ID, which is easily mistaken for a credential misconfiguration
in the integration.

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.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

@chemamartinez chemamartinez self-assigned this Apr 7, 2026
@chemamartinez chemamartinez added documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. enhancement New feature or request Integration:microsoft_exchange_online_message_trac Microsoft Exchange Online Message Trace Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] labels Apr 7, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 7, 2026

Vale Linting Results

Summary: 2 suggestions found

💡 Suggestions (2)
File Line Rule Message
packages/microsoft_exchange_online_message_trace/_dev/build/docs/README.md 36 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/microsoft_exchange_online_message_trace/docs/README.md 36 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

@chemamartinez chemamartinez marked this pull request as ready for review April 7, 2026 08:58
@chemamartinez chemamartinez requested a review from a team as a code owner April 7, 2026 08:58
@elasticmachine
Copy link
Copy Markdown

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@elastic-vault-github-plugin-prod
Copy link
Copy Markdown

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link
Copy Markdown

💚 Build Succeeded

cc @chemamartinez

Copy link
Copy Markdown
Contributor

@kcreddy kcreddy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@chemamartinez chemamartinez merged commit 17bc7af into elastic:main Apr 7, 2026
12 checks passed
@elastic-vault-github-plugin-prod
Copy link
Copy Markdown

Package microsoft_exchange_online_message_trace - 2.0.4 containing this change is available at https://epr.elastic.co/package/microsoft_exchange_online_message_trace/2.0.4/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. enhancement New feature or request Integration:microsoft_exchange_online_message_trac Microsoft Exchange Online Message Trace Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants