Enhance documentation with tenant verification details

[Prateek Taneja (prtanej)]

Added section on tenant verification and risk-based access for Microsoft Threat Intelligence APIs.

Important

Use the AI-powered workflow for Graph onboarding to author and self-review schema-related changes. See https://aka.ms/msgraphcdk for more information.

Required for API changes:

• [] Link to API.md file: ADD LINK HERE
• [] Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl): ADD LINK HERE

---

Add other supporting information, such as a description of the PR changes:

ADD INFORMATION HERE

---

Important

The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.

• do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
• Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
• If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
• After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
• Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

[learn-build-service-prod]

Learn Build status updates of commit d71c28d:

✅ Validation status: passed

File	Status	Preview URL	Details
api-reference/v1.0/resources/security-threatintelligence-overview.md	✅Succeeded

For more details, please refer to the build report.

[Prateek Taneja (prtanej)]

#sign-off

[Jarbas Horst (JarbasHorst)]

Hi Prateek Taneja (@prtanej), if you work for Microsoft, can you please create this PR in the private repository: https://github.com/microsoftgraph/microsoft-graph-docs/pulls. This simplifies the content verification by the content review team and align with our processes. Thanks!

[Prateek Taneja (prtanej)]

Hi Jarbas Horst (@JarbasHorst) - I don't have access to the private repo. Is there any documented guidance on how to request access? In any case, can this PR be processed and the following updates to other docs can be via the private repo once I have access?

[Regan Downer (v-regandowner)]

CC Danipocket for review

[Danipocket]

Prateek Taneja (@prtanej) and Regan Downer (@v-regandowner), minor and cosmetic changes can be proposed through this repo. Please refer internal users to our private repo.

[Prateek Taneja (prtanej)]

Are we good to merge this?

[Jarbas Horst (JarbasHorst)]

Hi Prateek Taneja (@prtanej), we should avoid using the possessive when the noun doesn’t refer to a person.

Suggested change

	The error message for a blocked request indicates the tenant's current verification state. When available, the message also includes a link to complete tenant verification.
	The error message for a blocked request indicates the current verification state of the tenant. When available, the message also includes a link to complete tenant verification.