… 35 unchanged lines …
  - "Certified" means certified for a model, not for every feature on the vendor's datasheet. Check which model the feature you're buying actually runs under.
  - Connect deployments often break Teams-native features agents expect — presence sync and transfers back into Teams queues need explicit design.
  - TPE doesn't honour Teams compliance recording. If the client's FCA recording obligation is met by a Teams policy-based recorder, TPE calls fall outside it.
+ - PSTN callers hear an announcement whenever recording starts or pauses on a TPE call with a Teams or dual-persona user. Learn's FAQ says partners suppress it by request to Microsoft. An October 2026 docs change adds a Teams meeting policy route (`DisableAudioAnnouncementsForResourceAccounts` set to `$true`, assigned to the resource account), but it wasn't on the live FAQ at the time of writing. Check which applies before promising a silent recording start.
  - TPE agents can't park calls or use shared line, and adding a Teams user ignores federation/external access config. Test transfer to Teams users early.
  - Mixing PSTN connectivity types between a resource account and transfer targets isn't supported. Integrations that look fine on a single trunk break when the client is half-way through a Direct Routing migration.
  - Unify vendors and TPE sit on Azure Communication Services, which retires as a standalone offering on 30 September 2028. TPE itself is unaffected, and it's now the supported route for Call Automation and PSTN. A vendor still running standalone ACS calling has a migration to do, so ask for their plan. See [ACS retirement: what lands on Teams voice](https://365-almanac.app/kb/teams/feature-acs-retirement-teams-voice-impact).

    … 37 unchanged lines …
  - TPE doesn't honour Teams compliance recording. If the client's FCA recording obligation is met by a Teams policy-based recorder, TPE calls fall outside it.
  - TPE agents can't park calls or use shared line, and adding a Teams user ignores federation/external access config. Test transfer to Teams users early.
  - Mixing PSTN connectivity types between a resource account and transfer targets isn't supported. Integrations that look fine on a single trunk break when the client is half-way through a Direct Routing migration.
+ - Unify vendors and TPE sit on Azure Communication Services, which retires as a standalone offering on 30 September 2028. TPE itself is unaffected, and it's now the supported route for Call Automation and PSTN. A vendor still running standalone ACS calling has a migration to do, so ask for their plan. See [ACS retirement: what lands on Teams voice](https://365-almanac.app/kb/teams/feature-acs-retirement-teams-voice-impact).
  - Extend solutions run bots in someone's Azure subscription — usually the vendor's. Ask where they're hosted and which region, because that's where call media is processed.
  
  ## Consultant notes