Startups: Companies that are in their initial stages of business and typically developing a business model and seeking financing.
Luiz Eduardo Piá de Andrade- What you’re experiencing is not expected behavior and is typically caused by the account being incorrectly associated with an existing Microsoft Entra (Azure AD) tenant that you don’t control (in this case, the EY directory).
When an account is linked to an external or unmanaged tenant:
- You may lack proper permissions to create subscriptions, VMs, or certain resources
- Azure services (like Speech Studio) can get stuck in authentication redirect loops
- Password and sign‑in behavior can appear unstable
- Support options may be limited because the account isn’t recognized as the billing or tenant owner
This also explains why: You could create some PaaS resources (like Speech Services), but not VMs
Creating a new directory was blocked
Using a directory created by another account “works,” but feels unofficial or unreliable
To make the account behave normally, the account must be cleanly associated with a tenant you own or control:
- Leave the external (EY) directory - Sign in to the Azure portal > Microsoft Entra ID > Manage tenants > Leave the EY tenant
- Create or use your own tenant
- Create a new Microsoft Entra tenant (or use one you own)
- Create a new Azure subscription under that tenant
- Ensure you are the Global Admin + Billing Owner
- Re‑test resource creation and sign‑in
- VM creation, Speech Studio access, and login loops should be resolved
Once the account is tied to a clean tenant with proper ownership, Azure behaves normally and support ticket creation becomes available.