Skip to content

Commit 9662ae4

Browse files
authored
Add context about new sign-in screen
As part of Microsoft's general commitment to security hardening, we are adding a new screen to the auto-acceleration and smartlinks sign-in flows. This screen is called the domain confirmation dialog and provides the user with an opportunity to confirm the domain of the tenant in which they are signing in to. Since this is a new screen being added to the auto-acceleration/smartlinks sign-in UI, we need to call this out in our documentation so customers can avoid concern when they see this new screen. ------- cc: @omondiatieno
1 parent 963d970 commit 9662ae4

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/active-directory/manage-apps/configure-authentication-for-federated-users-portal.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,11 @@ Some organizations configure domains in their Azure AD tenant to federate with a
2828

2929
For federated users with cloud-enabled credentials, such as SMS sign-in or FIDO keys, you should prevent sign-in auto-acceleration. See [Disable auto-acceleration sign-in](prevent-domain-hints-with-home-realm-discovery.md) to learn how to prevent domain hints with HRD.
3030

31+
> [!IMPORTANT]
32+
> Starting April 2023, organizations who use auto-acceleration or smartlinks may begin to see a new screen added to the sign-in UI. This screen, termed the Domain Confirmation Dialog, is part of Microsoft's general commitment to security hardening and requires the user to confirm the domain of the tenant in which they are signing in to. If you see the Domain Confirmation Dialog and do not recognize the tenant domain listed, you should cancel the authentication flow and contact your IT Admin.
33+
>
34+
> While the Domain Confirmation Dialog does not need to be shown for every instance of auto-acceleration or smartlinks, the presence of the Domain Confirmation Dialog means auto-acceleration and smartlinks can no longer proceed seamlessly when shown. Finally, given Microsoft identity platform manages the auto-acceleration sign-in flow end-to-end, the introduction of the Domain Confirmation Dialog should not result in any application breakages.
35+
3136
## Prerequisites
3237

3338
To configure HRD policy for an application in Azure AD, you need:

0 commit comments

Comments
 (0)