#Unable to login to deepgram
1 messages · Page 1 of 1 (latest)
Hey there! This channel allows you to ask Kapa.ai for assistance. But it looks like you haven't connected your Discord profile to your Deepgram account yet. You can do so at https://community.deepgram.com - by doing so, you'll be able to ask questions in #1115960287183511643 if you need human assistance!
Deepgram’s community offers tons of resources to support you on your voice AI journey
Hi @digital oak. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
You’re running into an SSO / identity change issue, which Deepgram doesn’t let you self-fix from the console.
From the knowledge sources, there are two relevant patterns:
-
If you can’t log in at all (password reset etc. doesn’t help)
Deepgram’s Help Center says to email Support with details so they can locate and fix your account issue.[Login help]- Email: [email protected]
- Include:
- The email address tied to your Deepgram account (the one used with Azure SSO)
- A clear description: that you originally signed up with Azure SSO on tenant A, your company has moved to tenant B, and you now cannot log in or recharge billing, and that this is blocking a production launch.
-
When SSO provider / identity changes
In a similar case (Google SSO → Microsoft/Azure SSO), Deepgram could not “transfer” the SSO identity, but they solved it by having the user create a new account with the new SSO and then sending a project invite so the user rejoined the existing project.[SSO change]Since you can’t access the old account to send yourself an invite, Support will need to:
- Verify your identity and project
- Either:
- Help you regain access to the existing account, or
- Invite your new Azure-tenant identity into the existing project so you can manage billing again.
Because this is blocking a go‑live and billing, you should:
- Immediately email
[email protected]with:- Subject like: “URGENT: Lost access due to Azure tenant change – need billing access”
- Old Azure login email and tenant info (if you have it)
- New Azure tenant / login you want to use
- Project ID(s) if you have them (from code, environment variables, or logs)
- If you don’t hear back quickly, you can also post in the Deepgram GitHub Discussions or Discord and reference that you’ve already emailed Support, but the primary path for account access is Support email.[Help Center]