Signing into Visual Studio subscriptions may fail when using aliases
Depending on the account type used to sign in, available subscriptions may not be correctly displayed when signing in to https://my.visualstudio.com. One potential cause is the use of "aliases" or "friendly names" in place of the sign-in identity to which the subscription is assigned. This is called "aliasing".
What is aliasing?
The term “aliasing” refers to users having different identities to sign in to Windows (or your Active Directory) and to access email.
Aliasing can be encountered when a company has a Microsoft Online Service for their directory sign-in, like 'JohnD@contoso.com', but users access their email accounts using aliases or friendly names, such as 'John.Doe@contoso.com'. Make sure your users are using the “Sign-in Email Address” as listed in the admin portal at https://manage.visualstudio.com to access their subscriptions.
What are the potential issues?
Depending on the subscriber’s account type, they may encounter one of two issues.
Work or school account UPN mismatch issue
A UPN mismatch can be encountered when a company has an Active Directory set up where the UserPrincipalName (UPN) is not same as the Primary SMTP Address.
How to detect if your sign-in address is impacted by a UPN mismatch
Sign into https://my.visualstudio.com/subscriptions using the sign-in address mentioned in your subscription assignment email.
Verify that the sign-in email address listed at the top right of the page matches the address you used to sign in. If it does not, your UPN is mismatched and you will not be able to view your subscription.
How to fix a UPN mismatch
Access the Visual Studio Administration Management portal https://manage.visualstudio.com
Locate the subscriber having the UPN mismatch issue. (The Filter feature can make it easy to find a subscriber.)
Change the sign-in mail address to the subscriber's UPN
Save the changes
Inform the subscriber to sign out of the subscriber portal and access again using the UPN
Personal account aliasing issue
Personal subscription accounts can also experience issues if the email address used to sign in to the Visual Studio Subscriptions portal does not match the email address associated with the subscription.
How to detect if your personal subscription account is impacted by an aliasing issue
Sign in to https://my.visualstudio.com/subscriptions
Verify that the sign-in email address listed at the top right of the page matches the address you used to sign in. If the signed-in email address is not the same as the email address used to access the website there is a conflict between your account and the alias.
How to fix an alias issue
The Visual Studio platform prioritizes the primary alias to show subscription details.
Go to Manage how you sign in to Microsoft. Sign in to your Microsoft account if prompted.
Under Account aliases, select Make primary next to the email address used to assign the subscription.
Sign out of the Visual Studio Subscriptions portal (https://my.visualstudio.com)
Sign back in using the account used to assign the subscription which should now be configured as primary alias.
Preventing aliasing issues
As an administrator, there are two options to ensure your subscribers have a successful sign-in experience on https://my.visualstudio.com.
- The first option (recommended), is to leverage the directory account as the sign-in for the Visual Studio Subscriptions portal at https://my.visualstudio.com.
- The second option (less secure), is to allow your subscribers to sign in using a different email address than their directory email address.
Both of these options are configured in the admin portal by completing the following steps:
Sign into https://manage.visualstudio.com
If you are altering a single user, select that user in the table and right click to edit. This will open a panel where you can modify the sign-in email address. Make the necessary updates in the sign-in email address field. Click save and the changes will take effect.
If you need to make these changes to a large quantity of users, you can utilize the bulk edit feature. Read the Edit multiple subscribers using bulk edit article for more information.
For both individual and bulk changes, the subscribers will receive an email with instructions that their sign-in email address has changed and they will need to sign in using the updated email address. It’s also important to note that if the subscriber previously activated benefits under the other sign-in address, they’ll need to continue using the other sign-in address to access them.
- Visual Studio documentation
- Azure DevOps documentation
- Azure documentation
- Microsoft 365 documentation
Learn more about managing Visual Studio subscriptions.