KamoCRM

Fall back to the org's own hostname for the Teams redirect

FeatureVOIPService
Shipped
4 செப்டம்பர், 2026 அன்று 11:41 PM UTC
Author
Kamo
Commit
10bc025

A redirect the org typed into its own registration still wins outright — Microsoft requires the URI replayed on the token exchange to match the authorization byte-for-byte, so whatever went into that Entra app is the only correct answer, and an existing connection must not move. What changes is the fallback under it. An org on its own app with no stored redirect was getting the platform hostname; it now gets api.<its own domain>, which is what its settings screen shows. An org on Kamo's multi-tenant app keeps the platform host, since that registration has one redirect and a per-org address against it is a mismatch. Both VOIP OAuth controllers already routed through this one method, so the org and member connect legs move together.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing