Remove the obsolete Entra licensing matrix

[Brian Santacruz (bsantacruzms)]

Why this change

The article contains an embedded Microsoft Entra edition and feature matrix that is no longer current. Licensing names, editions, and feature availability evolve independently of this Azure Security Fundamentals article, so a static matrix can give readers incorrect expectations when they evaluate identity capabilities or plan licensing.

Linking to the maintained Microsoft Entra licensing documentation gives readers a current source of truth and reduces the risk of security or purchasing decisions being based on obsolete information.

What changed

• Removed the obsolete Microsoft Entra licensing matrix.
• Updated the surrounding description of Microsoft Entra ID capabilities.
• Added a link to the maintained Microsoft Entra licensing guidance for current editions and feature availability.

Validation

• Confirmed the pull request updates only articles/security/fundamentals/overview.md.
• Ran git diff --check.
• Verified that the Microsoft Entra licensing link points to the maintained Microsoft Learn documentation.

References

• Microsoft Entra licensing

[prmerger-automator]

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

[prmerger-automator]

Brian Santacruz (@bsantacruzms) : 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 ea70d7e:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/security/fundamentals/overview.md	✅Succeeded

For more details, please refer to the build report.

[Brian Santacruz (bsantacruzms)]

sign-off

[Diana Richards (v-dirichards)]

Hi Brian Santacruz (@bsantacruzms) - This pull request was opened in the public repo. Microsoft contributors should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!

---

M. Baldwin (@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