Clarify cross-subscription connection limitations

[AhmadAbdullah91]

Added note about cross-subscription connections for model deployment.

[prmerger-automator]

@AhmadAbdullah91 : 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 e205b56:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/ai-foundry/how-to/connections-add.md	✅Succeeded

For more details, please refer to the build report.

[Copilot]

Pull Request Overview

This PR adds documentation to clarify limitations around cross-subscription connections in Azure AI Foundry. The change informs users that cross-subscription connections are not supported for model deployments.

• Added a note block explaining cross-subscription connection limitations for model deployment

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Grammar error: 'Cross-Subscription connections used for model deployment is not supported' should be 'Cross-subscription connections used for model deployment are not supported'.

Suggested change

	> Cross-Subscription connections used for model deployment is not supported (Azure AI Foundry, Azure OpenAI). You can't connect to resources from different subscription for model deployments.
	> Cross-subscription connections used for model deployment are not supported (Azure AI Foundry, Azure OpenAI). You can't connect to resources from different subscriptions for model deployments.

[Copilot]

Grammar error: 'from different subscription' should be 'from a different subscription'.

Suggested change

	> Cross-Subscription connections used for model deployment is not supported (Azure AI Foundry, Azure OpenAI). You can't connect to resources from different subscription for model deployments.
	> Cross-Subscription connections used for model deployment is not supported (Azure AI Foundry, Azure OpenAI). You can't connect to resources from a different subscription for model deployments.

[v-dirichards]

@sdgilley

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

[meerakurup]

#sign-off

[prmerger-automator]

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @sdgilley

[sdgilley]

#sign-off