Training: Instruction to develop new skills.
The behavior described matches common "No subscriptions found" and access issues after sign-in. Use the following checks and fixes, in order:
- Verify the correct directory (tenant) in Azure portal
- Sign in to the Azure portal with the alternate email that should have the FTE subscription.
- In the top-right corner, select the account name.
- Select Switch directory and check all listed directories.
- Select each directory in turn and go to Subscriptions to see if the FTE subscription appears.
No subscriptions foundeven if the subscription exists in another directory. - Confirm that the account has sufficient permissions on the subscription
If the correct directory is selected and the subscription still does not appear:
- The account might not be assigned a role on that subscription.
- Ask the subscription owner/admin (for the FTE subscription) to assign at least the Owner or another appropriate role to the alternate account on that subscription using Azure RBAC.
- Check sign-in issues caused by multiple accounts
If the portal signs in automatically as another user or directory:
- Clear browser cache and cookies.
- Or use a private browsing session (InPrivate/Incognito) and sign in again with the alternate email.
- Verify the FTE subscription is actually created and active
If, after switching directories and confirming permissions, no subscription appears at all:
- It is possible the subscription was not fully created or is blocked/flagged.
- In that case, create an Azure support request (using any available subscription or via the Azure support entry point) and provide details that this is an FTE subscription that is not visible after activation.
- If the alternate identity was changed
For Visual Studio-based benefits (including Azure credits) accessed via alternate identities:
- Ensure the Visual Studio subscription’s alternate account configuration is correct at https://my.visualstudio.com/subscriptions.
- If needed, remove and re-add the alternate work/school account, then sign in again to Azure with that account and repeat steps 1–3.
If none of the above resolves the issue, escalation through Azure support is required so the backend team can verify the subscription state and its association with the correct tenant and account.
References: