[Website]: Missing integration option in docs.

### Before you submit

- [x] This issue is about a documentation page, flow, or piece of content.

### Type of issue

Missing information

### What documentation page or section is affected

https://www.elastic.co/docs/reference/integrations/azure

### What happened?

I recommend including a section on this document that allows for a Registered Application to interface with Entra IdP APIs to integrate with Elastic.

Customers don't want the additional cost of standing up infrastructure for an Event Hub and may be willing to accept risk of some missing entries with an API integration.

Reference as an example of the concept: https://www.elastic.co/docs/reference/integrations/m365_defender

### Additional info

_No response_

---

TriageBot — Human needed

### 2026-07-09

**Type:** unclear

**Section check:**
- ❌ Unable to read issue body — content filtered by integrity policy (issue authored by an external user below the agent's required trust level)

**Next step:** A human team member should review this issue directly and re-run triage after confirming the content is safe and complete.

> Generated by [Gh Aw Issue Triage](https://github.com/elastic/docs-content/actions/runs/29001600779) for issue #7286 · 19.9 AIC · ⌖ 11 AIC · ⊞ 9.1K · [◷](https://github.com/search?q=repo%3Aelastic%2Fdocs-content+is%3Aissue+%22gh-aw-workflow-call-id%3A+elastic%2Fdocs-content%2Fgh-aw-issue-triage%22&type=issues)

Start with the affected Azure integration page at https://www.elastic.co/docs/reference/integrations/azure and compare its current options with the M365 Defender example at https://www.elastic.co/docs/reference/integrations/m365_defender. Determine the appropriate scope for documenting a Registered Application with Entra IdP APIs, then update the documentation so the supported integration path and its trade-offs are clear.

Written by the indexing model from the issue text.