E5 developer licenses not reflected on Azure (MCT benefits)

Cloud Ascent 1 Reputation point
2021-08-16T19:32:42.397+00:00

Dear all,

I am a Microsoft Certified Trainer, and as part of my benefits I created a new tenant, new domain.onmicrosoft.com from the visual studio portal after applying for the Microsoft 365 E5 developer subscriptions. So I have now 25 Microsoft 365 E5 licenses under my new office 365 tenant.
But what I care most about is reflecting those 25 licenses on the Azure portal.
Because the new tenant domain.onmicrosoft.com is different from the @harsh.com .com email which is linked to my MCT account, those 25 licenses are not being reflected on portal.azure.com when I sign in using the new tenant credentials.
When I tried to apply for Azure MSDN, it redirected me to my @harsh.com .com email linked to the MCT, and it created the MSDN subscription there. Yet, my 25 E5 licenses are not linked to the @harsh.com .com email, but to the newdomain.onmicrosoft.com office 365 account.

My end result which I'm trying to achieve:
Being able to use the 25 E5 licenses (which are benefits from MCT when I activated the Microsoft 365 E5 developer subscription) in Azure for the purpose of testing it as a lab for MCT preparation.
Reason:
Those E5 licenses already have Azure AD P1 and P2 licenses, whereas if I use azure from the @harsh.com .com account, I can apply for P1 or P2 for 1 month only which is not enough for me.

Your help will be more than appreciated.

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
37,794 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2021-08-16T19:40:13.813+00:00

    Visual studio (MSDN) subscriptions are not supported here on Q&A. You can submit a ticket here for support.
    https://visualstudio.microsoft.com/subscriptions/support/

    or chat online with them
    https://learn.microsoft.com/en-us/visualstudio/subscriptions/vs-concierge-chat

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments