Steps to Connect your organization to Azure AD are given below-
Sign in to your organization
Select gear icon Organization settings.
Screenshot showing highlighted Organization settings button.
Select Azure Active Directory, and then select Connect directory.
Select Connect directory to connect your organization to Azure AD
Select a directory from the dropdown menu, and then select Connect.
Select your Azure AD, and then Connect
If you can't find your directory, contact your Azure AD administrator and request that they add you as a member to the Azure AD.
Select Sign out.
Connect success dialog - select Sign out
Your organization is now connected to your Azure AD.
Confirm that the process is complete. Sign out, and then open your browser in a private session and sign in to your organization with your Azure AD or work credentials.
Sign back in to Azure DevOps and map any disconnected members to their Azure AD identities. Or, you can invite them as guests into the Azure AD.
Select Resolve to invite unmapped users
Mapping disconnected users
Inform users of the completed change
When you inform your users of the completed change, include the following tasks for each user in the organization to complete:
Clear the cache for the Git Credential Manager if you use Visual Studio or the Git command-line tool. Delete the cache file on each client machine.
Regenerate new personal access tokens. Complete the following steps:
a. In Azure DevOps, open your User profile, and then select Security from the resulting dropdown menu.
Select from your profile dropdown menu, Security
b. Select Personal access tokens, and then select New Token.
c. Complete the form, and then select Create.
d. When the token is created, copy it, as it can't be viewed again.
Request that SSH keys be manually cleared by Support, and then recreate SSH keys. Complete the following steps.
a. In Azure DevOps, open your User profile, and then select Security from the resulting dropdown menu.
Select from your profile dropdown menu, Security
b. Select SSH public keys, and then select Add.
c. Enter a description and key data, and then select Save.
d. When the token's created, copy it, as it can't be viewed again.
Rename your Microsoft account to a different email that doesn't conflict with your Azure AD identity. Doing so ensures that you won't be prompted to choose between accounts.
Adjust your Visual Studio subscription if the UPN used inside your Azure DevOps organization has changed. You can have it reassigned to your new UPN, or set that UPN as the alternate account inside the subscription.
Successfully connected
Regards,
Rachel Gomez
