Skip to content

Commit f79df45

Browse files
Merge pull request #230677 from pritamso/Broken-link-fix-croblesm
Broken link fix
2 parents 2702929 + 2ee9a09 commit f79df45

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/dms/tutorial-login-migration-ads.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Before you begin the tutorial:
6363
>
6464
> Nevertheless, the login migration process can be performed at any time, to update the user mapping synchronization for recently migrated databases.
6565
66-
- For Windows accounts, ensure that the target SQL managed instance has Azure Active Directory read access. This option can be configured via the Azure portal by a user with the Global Administrator role. For more information, see [Provision Azure AD admin (SQL Managed Instance)](/sql/database/authentication-aad-configure#provision-azure-ad-admin-sql-managed-instance).
66+
- For Windows accounts, ensure that the target SQL managed instance has Azure Active Directory read access. This option can be configured via the Azure portal by a user with the Global Administrator role. For more information, see [Provision Azure AD admin (SQL Managed Instance)](/azure/azure-sql/database/authentication-aad-configure#provision-azure-ad-admin-sql-managed-instance).
6767

6868
Domain federation between local Active Directory Domain Services (AD DS) and Azure Active Directory (Azure AD) has to be set up by an administrator. This configuration is required so that the on-premises Windows users can be synced with the company Azure AD. The login migrations process would then be able to create an external login for the corresponding Azure AD user in the target managed instance.
6969

0 commit comments

Comments
 (0)