Close: DataProtectionKeys table does not have a Discriminator column

[Copilot]

Issue reports a missing Discriminator column in the DataProtectionKeys table documentation. After verification, the docs are correct — no change needed.

DataProtectionKey is a standalone entity with no inheritance hierarchy, so EF Core never generates a Discriminator column (that's TPH-only). Confirmed against:

• DataProtectionKey.cs — three properties: Id, FriendlyName, Xml
• Official sample migration — three columns, no discriminator

The existing table in the docs is accurate. Closing as not-a-bug.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Missing Discriminator column in the table example.</issue_title>
<issue_description>### Description

There is a missing Discriminator column in the table example.

Page URL

https://learn.microsoft.com/en-gb/aspnet/core/security/data-protection/implementation/key-storage-providers?view=aspnetcore-8.0&tabs=visual-studio

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/security/data-protection/implementation/key-storage-providers.md

Document ID

7d481dae-d27d-909c-a35d-bad66c7508d2

Article author

@Rick-Anderson</issue_description>

<agent_instructions>he actual product source code for DataProtectionKey and the official EF Core sample migration, the DataProtectionKey class has no inheritance hierarchy, meaning a Discriminator column is not part of the default schema. The current documentation table may actually be correct and the issue is not or no longer is a valid one. If so, then close the issue with that note and close any PR you may have created with that note.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Missing Discriminator column in the table example. #32577

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.