Skip to content

Commit 2cea712

Browse files
Merge pull request #242963 from FaithOmbongi/patch-5
Update Graph link for authenticationBehaviors
2 parents 14e54cb + 2c343dc commit 2cea712

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/active-directory/develop/migrate-off-email-claim-authorization.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ This risk of unauthorized access has only been found in multi-tenant apps, as a
4343

4444
To secure applications from mistakes with unverified email addresses, all new multi-tenant applications are automatically opted-in to a new default behavior that removes email addresses with unverified domain owners from tokens as of June 2023. This behavior is not enabled for single-tenant applications and multi-tenant applications with previous sign-in activity with domain-owner unverified email addresses.
4545

46-
Depending on your scenario, you may determine that your application's tokens should continue receiving unverified emails. While not recommended for most applications, you may disable the default behavior by setting the `removeUnverifiedEmailClaim` property in the [Authentication Behaviors Microsoft Graph API](/graph/api/resources/authenticationbehaviors).
46+
Depending on your scenario, you may determine that your application's tokens should continue receiving unverified emails. While not recommended for most applications, you may disable the default behavior by setting the `removeUnverifiedEmailClaim` property in the [authenticationBehaviors object of the applications API in Microsoft Graph](/graph/applications-authenticationbehaviors).
4747

4848
By setting `removeUnverifiedEmailClaim` to `false`, your application will receive `email` claims that are potentially unverified and subject users to account takeover risk. If you're disabling this behavior in order to not break user login flows, it's highly recommended to migrate to a uniquely identifying token claim mapping as soon as possible, as described in the guidance below.
4949

@@ -125,4 +125,4 @@ If your application uses `email` (or any other mutable claim) for authorization
125125
## Next steps
126126

127127
- To learn more about using claims-based authorization securely, see [Secure applications and APIs by validating claims](claims-validation.md)
128-
- For more information about optional claims, see the [optional claims reference](./optional-claims-reference.md)
128+
- For more information about optional claims, see the [optional claims reference](./optional-claims-reference.md)

0 commit comments

Comments
 (0)