@Felix Gravila welcome to the Microsoft Q&A community.
It sounds like a frustrating situation! Here's what might be happening and some steps you can take:
Why This Happens
Your private email might have been inadvertently linked to your union's Azure tenant. This can happen if:
- Someone added your email to their organization's Azure Active Directory (AAD) without your knowledge.
- You were part of an event or training where your email was used to access Azure resources, and it got associated with their tenant.
- A misconfiguration or error occurred during account setup.
What You Can Do Now
- Try Accessing Azure with a Tenant ID: If you know the tenant ID of your union's Azure account, you can try logging in using a URL like
https://portal.azure.com/<tenantID>
. This might allow you to access the account and check its settings. - Use Azure CLI: Install the Azure CLI and try logging in with your email. You can use commands like
az login
to see if your account is associated with multiple tenants. - Contact Microsoft Support: Even if you can't log in, you can reach out to Microsoft Support directly through their support page or via phone. Explain the situation and request assistance in unlinking your email from the union's tenant.
- Clear Browser Cache: Sometimes, cached credentials can cause login issues. Try clearing your browser cache or using an incognito window to log in.
- Check Your Microsoft Account: Log in to your Microsoft account at account.microsoft.com and check if your email is linked to any organizations under "Organizations."
Next Steps
Since you're planning to contact your union on Monday, you can ask them to remove your email from their Azure tenant. They can do this through their Azure portal by navigating to "Users" in their AAD and removing your account.
I hope these helps. Let me know if you have any further questions or need additional assistance.
Also if these answers your query, do click the "Upvote" and click "Accept the answer" of which might be beneficial to other community members reading this thread.