Hi VAPI Support, I need help removing Azure OpenAI as a fallback provider from my VAPI organization. Azure is currently configured at the organization/integration level and is causing call ejections when OpenAI fails (Azure credentials are invalid). I've tried: 1. VAPI Dashboard → Settings → Integrations (no remove/delete option visible) 2. VAPI CLI (no integrations command available) 3. VAPI API (integrations endpoint returns 404) Could you please: 1. Remove Azure OpenAI integration from my organization (Org ID: 9ba4e698-78d2-4ed5-86ac-1081633f4fe3) 2. Or provide instructions on how to remove it via dashboard/CLI/API Evidence: - Call ID: 019b4de4-d169-7001-842a-02df87bba823 - Error: pipeline-error-azure-openai-llm-failed - Assistants are clean (no Azure in assistant configs) Desired: Use Google Gemini as fallback instead of Azure. Thank you! https://cdn.discordapp.com/attachments/1453404083322093722/1453404083762237551/VAPI_Support_Ticket__Remove_Azure_OpenAI_Integration.pdf?ex=694d5388&is=694c0208&hm=de1d66c0eb582ccc3dcc3cdc6e83f9a784cf80c4f53a91f3140b9064948941c4&

Thanks for the detailed context — the core issue here is that Azure is still registered at the org/integration level, so VAPI is invoking it as a global fallback even though no assistants reference it, which is what’s causing the call ejections. I can help you resolve this cleanly by removing or overriding the org-level Azure integration and validating Gemini as the fallback path. In practice, this usually requires either a backend removal by VAPI support or a specific org-level config update that isn’t exposed in the dashboard yet. Before proceeding, can you confirm whether Gemini is already connected at the organization level or only at the assistant level? @Dave

Thanks for getting back to me so quickly @User Yes, Gemini is installed, and it has a valid and active key. It is installed at the account level. The Assistant level only offers one model integration, and that's already set to OpenAI for the assistant in question.