docs: 📝 add more information on Key Vault control/date plane actions

[krukowskid]

No description provided.

[prmerger-automator]

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

[prmerger-automator]

@krukowskid : 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 36562b4:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/key-vault/general/network-security.md	✅Succeeded

For more details, please refer to the build report.

[Court72]

@msmbaldwin

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

[v-dirichards]

@msmbaldwin Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?

Thanks!

[github-actions]

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

[Copilot]

Pull Request Overview

This PR enhances the Key Vault network security documentation by adding more detailed information about the distinction between control plane and data plane operations and their implications for network access restrictions.

• Removes a generic statement about firewall rules applying only to data plane operations
• Adds comprehensive explanation of how certain Key Vault operations can be executed through both control and data planes
• Clarifies that control plane operations bypass network access restrictions and are governed solely by Azure RBAC

---

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