Merge pull request #7683 from mikkelhm/main

Remove documentation for a User Group Claim Name property that is wrong

Author: eshanrnh

umbraco-cloud/begin-your-cloud-journey/project-features/external-login-providers.md

@@ -183,7 +183,7 @@ Learn about what type of data and information you need for each field in the con
 
 <td>Your provider may assign users to specific roles (For example: Admin, Editor, Viewer).<br><br>The <strong>User Group Claim Name</strong> is the field in the authentication token (claim) that identifies these roles. The system reads this claim to determine a user’s permissions.<br><br>Example: If your provider sends roles in a claim named <code>user_roles</code>, you would set the <strong>User Group Claim Name</strong> to <code>user_roles</code> so the system can properly recognize user permissions.<br><br><strong>NOTE:</strong> If the field is left blank, the system will default to use <code>http://schemas.microsoft.com/ws/2008/06/identity/claims/role</code> as the claim name.</td>
 
-<td>Entra ID: <code>email (ID)</code>, <code>groups</code></td></tr>
+<td>Entra ID: <code>groups</code></td></tr>
 
 <tr><td>Metadata Address</td><td>If you need a special metadata address for your External Login Provider, you can set it here. By default, the system will resolve the metadata address from the Authority URL, which is why this property is optional.</td><td>A common scenario for using a special metadata address is when working with Entra ID and configuring claims mapping. In this case, you must set the metadata address to the following:<code>https://login.microsoftonline.com/{tenant}/v2.0/.well-known/openid-configuration?appid={client-id}</code>.</td></tr></tbody></table>