Update managed integrations FAQ with metering details

[nimarezainia]

Added metering information for managed integrations starting September 2026.

notify users when billing commences.

We are working on comm to the customers on when billing will commence. Support is asking us to have something in the docs as well. I am not sure if we can use dates as such in our docs.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• [ x] No

2. If you answered "Yes" to the previous question, please specify the tool(s) and model(s) used (e.g., Google Gemini, OpenAI ChatGPT-4, etc.).

Tool(s) and model(s) used:
-->

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: completed. View progress.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• manage-data/ingest/managed-integrations/managed-integrations-faq.md

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

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.

[github-actions]

Docs review summary

Focus areas

• Style and clarity: Minor Vale suggestions in unchanged sections (first-person "my", "abuse", "take action"); none introduced by this diff. The added date phrasing ("1st of September 2026") doesn't match the style guide date format — see inline comment.
• Jargon: None found in the added sentence.
• Frontmatter and applies_to: Unchanged; no issues in the diff.
• Content type fit: No change — FAQ format preserved.
• Contradictions: 1 found (local) — see inline comment. The new sentence implies {{ech}} metering isn't yet active, but the paragraph above states billing is already charged per hour.
• Parent issue satisfaction: Not applicable (no linked issue).

Notes

• The PR body itself raises an open question about whether using a specific future date is appropriate for the docs — worth resolving with the author/PM before merge, independent of the wording fix.

Generated by Docs review agent for #7899 · sonnet50 · 23.1 AIC · ⌖ 3.9 AIC · ⊞ 17.2K

[github-actions]

This new sentence appears to contradict the paragraph it's added to. Two lines above, the page states "each deployed {{managed-integration}} is charged per hour" as a current, already-effective fact — but this sentence says metering "will commence 1st of September 2026," implying billing hasn't started yet. Please clarify whether {{ech}} managed-integration billing is already active (and this date refers to something else, e.g. a pricing/tier change) or genuinely starts on that date (in which case the earlier sentence needs to reflect that it isn't billed yet). Also, per the formatting style guide, write the date as September 1, 2026 instead of 1st of September 2026.

Suggested change

	| abuse.ch API | 2 |
	For current pricing details, refer to the [Elastic pricing page](https://www.elastic.co/pricing). Metering {{managed-integrations}} on {{ech}} deployments will commence on September 1, 2026.

[florent-leborgne]

LGTM with a suggestion on the wording to make it "timeless"

[florent-leborgne]

Suggested change

	For current pricing details, refer to the [Elastic pricing page](https://www.elastic.co/pricing). Metering {{managed-integrations}} on {{ech}} deployments will commence 1st of September 2026.
	For current pricing details, refer to the [Elastic pricing page](https://www.elastic.co/pricing). Elastic meters {{managed-integrations}} on {{ech}} deployments as of September 1, 2026.

Suggesting some phrasing that doesn't warrant an immediate update once the date passes