Fix tenant ID header name in validation instructions

[zaidmohd]

Fix tenant ID header name in validation instructions

This pull request corrects the HTTP header name for tenant ID validation in Step 5.3 of the "Publish agents to Microsoft 365 Copilot and Microsoft Teams by using the REST API" article.

Change

• Section 5.3 stated the Bot Channel Adapter sends the caller's tenant ID in the x-tenant-id header. The actual header is x-ms-tenant-id. Following the doc as written, a tenant-validation check would read an empty header and reject every request (or, if written to fail open, provide no protection at all).

Evidence

Verified via live inbound header capture on an M365 Copilot → Bot Channel Adapter → backend flow (app-identity / SingleTenant bot registration, matching the msaAppType: 'SingleTenant' config in Step 2 of this article):

• The inbound POST from the Channel Adapter carries x-ms-tenant-id (value = originating Entra tenant, consistent with the serviceUrl tenant segment), alongside x-ms-conversation-id.
• No x-tenant-id header is present on the request.
• The x-ms- prefix is consistent with the adapter's other headers (x-ms-conversation-id).

The header is emitted by Microsoft's Bot Channel Adapter, which is the same hop for both App Service–hosted and Foundry-hosted agents, so the corrected name applies to the Foundry VNet scenario described here.

[prmerger-automator]

@zaidmohd : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[prmerger-automator]

@zaidmohd : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 310960e:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/foundry/agents/how-to/publish-copilot-virtual-network.md	✅Succeeded

For more details, please refer to the build report.

[v-regandowner]

@fosteramanda

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team