add new private connectivity limitation (motlp)

[shainaraskas]

Summary

• We missed a limitation: in ECH private connectivity does not secure the mOTLP endpoint
• I added the limitation, and we decided to make the limitations more visible by rolling them into the tutorials
• I suspect the transport client limitation was also missing from azure/gcp. will get alex to confirm during review :)

second PR: add this limitation to the motlp docs elastic/opentelemetry#562

asking for a review from the ingest folks to validate the language is not weird

context thread (internal)

Generative AI disclosure

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

• Yes
• 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:
cursor auto

[github-actions]

🔍 Preview links for changed docs

• deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md
• deploy-manage/security/private-connectivity-aws.md
• deploy-manage/security/private-connectivity-azure.md
• deploy-manage/security/private-connectivity-gcp.md

[github-actions]

Vale Linting Results

Summary: 1 warning found

⚠️ Warnings (1)

File	Line	Rule	Message
deploy-manage/security/_snippets/private-connectivity-limitations-ech.md	3	Elastic.DontUse	Don't use 'just'.

---

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.

[theletterf]

+CC @mlunadia @vigneshshanmugam

[vigneshshanmugam]

mOTLP changes LGTM, I ll let other reviewers approve.