Integrations · guide

Microsoft Teams with Amazon Connect

Microsoft Teams to Amazon Connect

Verified 2026-09-25 · 65 sources · tier 2–3

For Contact-center and Teams voice administrators who need to transfer calls from Amazon Connect to Microsoft Teams users..

Amazon Connect can transfer customer contacts to Microsoft Teams users using public telecommunications carriers or session border controllers 19​18. Direct Routing integrates Teams with certified Session Border Controllers, while phone number quick connects transfer contacts to external numbers 18​26.

Before you start

  • Ensure each target Microsoft Teams user holds a Teams Phone license and has an active PSTN connectivity solution configured 20. A Microsoft Teams tenant can combine Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing 19.
  • In Amazon Connect, confirm an active instance is available with claimed DID or toll-free numbers 55.
  • Note that an Amazon Connect account by default can claim and release up to 200% of its phone-number quota in a rolling 180-day period 56, and a released phone number cannot be claimed again 57.

What changes by situation

Pick your answers to see only your path. Nothing is sent anywhere until you make a plan.

How will calls get from Amazon Connect to the Teams user?
Who starts the transfer to the Teams user?
How will the agent know whether the Teams user is available?

Three questions. One permanent page you can send to your manager.

Step 1 Confirm each Teams target can receive an external call

Do

Verify that every Microsoft Teams user who will receive transferred calls is assigned a Teams Phone license and an active PSTN connectivity option 20.

Verify

Suggested check: Open the administrative directory and confirm each target user displays an assigned telephone number and an active voice routing entitlement.

Rollback

Suggested rollback: Remove or unassign the telephone number and license from the user account.

Step 2 Give each Teams target a number Amazon Connect can reach

Over the public switched telephone network (PSTN)

Do

Assign each target user a public phone number using Calling Plan, Operator Connect, Teams Phone Mobile, or Direct Routing 19. Format the number with the country code in full E.164 format for Amazon Connect quick connect configurations 23​58.

Verify

Suggested check: Place an external telephone call to the assigned E.164 number and confirm the call rings the target client.

Rollback

Suggested rollback: Remove the assigned phone number from the user account within the carrier management portal.

Over SIP into Teams Direct Routing via an SBC

Do

Assign each target user a Direct Routing number using PowerShell cmdlet Set-CsPhoneNumberAssignment -PhoneNumber <number> -PhoneNumberType DirectRouting, which enables Enterprise Voice 40. Ensure the number is formatted in full E.164 format 40. Place the users in Teams Only mode (UpgradeToTeams TeamsUpgradePolicy) so incoming calls land directly in the Microsoft Teams client 42. If multiple users share a base number with individual extensions, format the incoming SIP INVITE Request-URI to include the ;ext= parameter for user lookup 41.

Verify

In the Microsoft Teams admin center, check that the user profile displays the assigned telephone number with a phone number type of Direct Routing 40.

Rollback

Suggested rollback: Modify or clear the assigned phone number on the user object using administrative interfaces.

Step 3 Pair the SBC with Teams Direct Routing

Over the public switched telephone network (PSTN)

Do

Maintain the existing PSTN carrier integration without deploying an intermediate Session Border Controller (SBC) for this path 19.

Verify

Suggested check: Confirm that inbound PSTN routing remains functional to target users.

Rollback

Suggested rollback: No configuration was altered; no rollback action is required.

Over SIP into Teams Direct Routing via an SBC

Do

Pair the certified Session Border Controller (SBC) with Teams Direct Routing using the PowerShell cmdlet New-CsOnlinePSTNGateway by specifying FQDN, SipSignalingPort, MaxConcurrentSessions, and Enabled, or configure it in the Teams admin center under Voice > Direct Routing > SBCs 31​18. Ensure the domain portion of the SBC FQDN is registered in the tenant, is not *.onmicrosoft.com, and that at least one user in that domain holds an E3 or E5 license 30. Configure the SBC to enforce TLS 1.2 using one of Microsoft's supported ECDHE-RSA AES cipher suites 32. Build custom online voice routing policies containing PSTN usages and voice routes for assignment to specific users, avoiding modifications to the global voice routing policy that could divert Calling Plan or Operator Connect users to the trunk 44​45.

Verify

Run Get-CsOnlinePSTNGateway and confirm the SBC is listed with Enabled set to True 33. On the SBC interface, verify that outgoing SIP OPTIONS messages sent to Direct Routing receive a 200 OK response and that the SBC answers incoming Direct Routing SIP OPTIONS with a 200 OK 33.

Rollback

Set the SBC Enabled parameter to False using Set-CsOnlinePSTNGateway to take the SBC out of service temporarily 29​59.

Step 4 Open the outbound path in Amazon Connect

Over the public switched telephone network (PSTN)

Do

Verify that the Amazon Connect instance is allowlisted to dial the destination country of the target Teams phone numbers, submitting an Amazon Connect service quota increase request if the country is not allowlisted 37. Configure an Outbound caller ID number on the Amazon Connect queue using a claimed or ported number, which AWS requires to execute outbound calling 27​60. Ensure agents have the CCP outbound calling permission enabled, as missing permissions or unconfigured caller IDs trigger an Invalid outbound configuration error 61.

Verify

Suggested check: Open the queue configuration page in the admin console and confirm an outbound caller ID number is selected and saved.

Rollback

Suggested rollback: Remove the assigned outbound caller ID number from the queue settings in the admin console.

Over SIP into Teams Direct Routing via an SBC

Do

Confirm the Amazon Connect instance is deployed in an AWS Region that supports external voice transfer connectors, noting that connectors are billed at $100 per connector per day 62. Configure the outbound connection routes targeting the SBC host, signaling port, and transport protocol 31.

Verify

Suggested check: Confirm in the administrative interface that the external connector status is active and operational.

Rollback

Suggested rollback: Delete or disable the external voice connector routes in the environment.

Step 5 Deliver Connect-originated calls to the Teams user

Over the public switched telephone network (PSTN)

Do

Route outbound PSTN calls directly through the existing public carrier network to the target Teams numbers 19.

Verify

Suggested check: Place an outbound test call to an external test number to ensure carrier trunk egress is functional.

Rollback

Suggested rollback: No intermediary SBC routing adjustments are needed.

Over SIP into Teams Direct Routing via an SBC

Do

On the SBC, configure routing rules to deliver calls originating from Amazon Connect to the Microsoft Teams Direct Routing trunk 18. Format the SIP Request-URI to present the Teams user's assigned number in E.164 format, appending ;ext= when target users share a base number with extensions 41. To divert an incoming call straight to a target user's voicemail without ringing the client, append opaque=app:voicemail to the SIP Request-URI 43. Configure the SBC and intermediate firewalls to permit incoming signaling connections from all Microsoft signaling IP addresses, because SIP REFER requests can arrive across separate TLS connections from different addresses 49.

Verify

Suggested check: Route a SIP test call through the SBC into Direct Routing and confirm the targeted endpoint rings.

Rollback

Suggested rollback: Remove or disable the SBC routing rule that directs traffic to the SIP proxy.

Step 6 Build the transfer destination in Amazon Connect

An agent in the Contact Control Panel (CCP) + Over the public switched telephone network (PSTN)

Do

In the Amazon Connect console, create a Phone number quick connect for each target Microsoft Teams user and enter the phone number with the country code in E.164 format 26​23. Attach the quick connect to an inbound queue 21. Assign that queue to the routing profiles used by transferring agents 48. Because phone number quick connects do not invoke a flow, the outbound caller ID cannot be set per transfer and will reflect the queue's outbound caller ID configuration 25​63.

Verify

Sign in to the Contact Control Panel (CCP) as an agent and confirm that the external quick connects are visible in the CCP interface at all times 24.

Rollback

Remove the quick connect from the queue configuration to prevent agents from viewing and selecting it in the CCP 21.

An automated contact flow + Over the public switched telephone network (PSTN)

Do

In the Amazon Connect flow designer, insert a Transfer to phone number block into an Inbound or Customer Queue flow 38. Configure a timeout value, and route the Call Failed, Timeout, and Error branches to an appropriate fallback flow or queue 34. If the call should return to the flow when the Teams user hangs up, enable the Resume flow after disconnect property, noting that this functions only when the external party disconnects and will terminate the call if the customer disconnects 39. Outside the United States, configure an Amazon Connect number under Caller ID number, noting that in Australia and the United Kingdom carriers may reject calls with non-compliant caller IDs 35; if no custom caller ID is configured, the customer's caller ID is passed through 36.

Verify

Place a test call into the inbound flow and verify that answering the call at the Teams client triggers the Success branch of the block 34.

Rollback

Suggested rollback: Revert to and publish a previous version of the contact flow that does not contain the Transfer to phone number block.

An agent in the Contact Control Panel (CCP) + Over SIP into Teams Direct Routing via an SBC

Do

Create a Transfer to Queue flow that sets the external connector ARN as an attribute and routes through a Transfer to phone number block, noting that this flow-block combination handles voice contacts only 38. WarmTransfer's reading of the sources is that an agent transfer over an external voice connector can be exposed using a queue quick connect pointing to a Transfer to Queue flow, because phone number quick connects cannot invoke a flow 7​28​47. Add the queue quick connect to a queue included in the transferring agents' routing profiles 21​48.

Verify

In the Contact Control Panel (CCP), confirm that the queue quick connect appears only when an agent is on an active call 24.

Rollback

Remove the queue quick connect from the queue configuration in the Amazon Connect admin portal 21.

An automated contact flow + Over SIP into Teams Direct Routing via an SBC

Do

In an Inbound or Customer Queue flow, set the external connector ARN as a contact attribute, and add a Transfer to phone number block targeted to that attribute 38. Configure the timeout value and wire the Call Failed, Timeout, and Error branches to fallback handling 34.

Verify

Initiate a test interaction into the contact flow and confirm that the call executes through the connector to ring the Microsoft Teams user 34.

Rollback

Suggested rollback: Revert to and publish the previous version of the flow.

Step 7 Decide what the agent sees about Teams availability

No presence integration

Do

WarmTransfer's reading of the sources is that native Amazon Connect quick connects and CCP transfers do not display Teams user availability 5. External quick connects appear in the CCP at all times 24.

Verify

Suggested check: Verify that agents understand the transfer list in CCP does not reflect external user status.

Rollback

Suggested rollback: No configuration rollback is required.

Custom integration via Microsoft Graph

Do

Register an enterprise application in Microsoft Entra ID and grant it the application permission Presence.Read.All, which is the least privileged permission required to read other users' presence 14. Query user presence via HTTP GET requests to /users/{id}/presence or /communications/presences/{id}, passing the target user's Entra object GUID, noting that application permissions cannot use the /me path 13​14. Design the API polling integration to stay within the limit of 1,500 requests per 30 seconds per application per tenant 15. Note that this Microsoft Graph presence API is supported in the global service as well as US Government L4 and L5 (DoD) environments, but is not available in China operated by 21Vianet 12.

Verify

Execute a test GET request to /users/{id}/presence for a target user GUID and verify that the response returns valid availability and activity strings 13.

Rollback

Suggested rollback: Revoke the application permission grant from the registered application in the identity admin center.

Third-party AWS Marketplace product

Do

Evaluate third-party AWS Marketplace solutions designed for Teams and Amazon Connect presence synchronization 16​17. CloudInteract states in its Marketplace listing that its product transfers PSTN calls from Connect to Teams, displays target Teams status to agents, and requires no Teams Phone licenses 16. NeuraFlash states in its Marketplace listing that its product displays colleague availability inside the Amazon Connect Agent Workspace, updates an agent's Teams status to Do Not Disturb during calls, and supports transfers 17.

Verify

Suggested check: Confirm inside the agent workspace that the displayed presence matches the actual presence status of a pilot Teams user.

Rollback

Suggested rollback: Uninstall the third-party application package and revoke any associated cloud identity permissions.

Step 8 Run the transfer

An agent in the Contact Control Panel (CCP)

Do

During an active call in the Contact Control Panel (CCP), the agent chooses Quick connects to pick a configured Teams destination, or selects Number pad to manually dial an external number 6. When the transfer begins, Amazon Connect places the caller on hold and connects the agent to the transfer destination 3. While on hold, the customer hears the configured Customer hold flow 22. Once the Microsoft Teams target answers, the agent can choose Join to form a conference among the customer, the Teams user, and the agent 4. To complete the transfer, the agent chooses Leave to disconnect from the interaction while leaving the customer and Teams user connected 4.

Verify

Confirm that after the agent clicks Leave, the audio path between the customer and the Microsoft Teams recipient remains active 4.

Rollback

Suggested rollback: Before choosing Leave, disconnect the outbound consultation leg in the CCP interface to return to the original customer call on hold.

An automated contact flow

Do

Monitor the flow's Call Failed, Timeout, and Error branches to ensure proper handling during automated transfers 34.

Verify

Verify in flow metrics that successfully transferred calls take the Success branch and abandoned or rejected calls take the Timeout or Call Failed branches 34.

Rollback

Suggested rollback: Adjust contact flow branch logic to re-route calls to an agent queue if automated transfer failures occur.

Step 9 Handle the Teams user transferring the caller onward

Over the public switched telephone network (PSTN)

Do

Test onward transfers directly on the specific PSTN service in use, noting that Microsoft's Direct Routing call-transfer guidance does not apply to Calling Plan or Operator Connect deployments 54.

Verify

Suggested check: Have the user transfer an active call onward to another internal or external recipient, and verify audio continuity.

Rollback

Suggested rollback: No SBC parameters are configured for this carrier path; no rollback is required.

Over SIP into Teams Direct Routing via an SBC

Do

Microsoft Teams attempts Direct Routing call transfers using SIP REFER first, then INVITE with Replaces, and finally an internal method invisible to the SBC if neither is supported 53. When a SIP REFER is received from Teams, configure the SBC to send a new INVITE back to the Microsoft SIP proxy with the Request-URI set to the Refer-To string and the Referred-By header copied unchanged, even for PSTN destinations 52. For consultative transfers, ensure the SBC returns 202 Accepted and sends NOTIFY messages reporting transfer progress, as the Microsoft SIP proxy drops the original leg only upon receiving a NOTIFY with 200 OK 51. Note that since June 2026, Microsoft terminates a blind-transferred Direct Routing call as soon as the SBC accepts the REFER, without waiting for the transfer outcome 50. If the forwarded or transferred call is routed back out to the PSTN, Direct Routing prioritizes the ingress SBC over other configured SBC routes regardless of priority settings 46.

Verify

Perform both consultative and blind transfers from the Microsoft Teams client and verify in SBC signaling traces that NOTIFY or REFER handling completes without call drops 51​50.

Rollback

Suggested rollback: Revert SBC SIP manipulation profiles and REFER routing configurations to their previous settings.

Step 10 Test end to end and read the records

Do

When transferring via phone number quick connects, verify that the Microsoft Teams user receives the queue's outbound caller ID 25. When using a Transfer to phone number block without a custom caller ID set, verify that the Teams user receives the calling customer's caller ID 36. Note that external transfers remain anchored to the Amazon Connect instance Region for the entire call duration, incurring per-minute usage until the transfer recipient disconnects, and call recording stops once the agent drops or the transfer completes 64. AWS advises avoiding circular transfers that send calls back into Amazon Connect, as PSTN latency compounds 65.

Verify

In Amazon Connect contact search, locate the completed test call and confirm that multiple contact records are generated, linked together by their initial, next, and previous contactId fields 2.

Rollback

Suggested rollback: No configuration change is made during verification; no rollback is required.

See also

Applicability

Applies to: Amazon Web Services Amazon Connect, Microsoft Graph, CloudInteract Microsoft Teams Integration for Amazon Connect, NeuraFlash Teams Integration for Amazon Connect, Microsoft Teams Phone Direct Routing, and Microsoft Teams Phone. Deployments: multi-tenant. Sources checked 2026-09-25. The Microsoft Graph get-presence API is not available in China operated by 21Vianet 12. Microsoft Direct Routing blind transfer behavior changes apply from June 2026 onward 50. Claims for external voice connector daily rates apply to the us-west-2 Region 62.

What remains uncertain

The specific Session Border Controller SIP, TLS, and media codec requirements on the interface facing the Amazon Connect external voice transfer connector are not covered by the sources below. The administrative procedure and API parameters for deleting an Amazon Connect external voice transfer connector to stop daily recurring charges are not covered by the sources below. The specific PowerShell cmdlet to remove a Direct Routing phone number assignment from a Teams user is not covered by the sources below. The exact Contact Control Panel graphical controls for cancelling an in-progress transfer consult before choosing Join or Leave are not covered by the sources below.

See also

Related

Referenced by

Sources

  1. 1
    For the separate conversational analytics (Contact Lens) connector, the external voice system sends SIPREC audio to the fully qualified host name shown on the connector details page.
  2. 2
    A customer can have multiple contact records because a record completes when the flow or agent interaction ends; linked records share initial, next and previous contactId fields.
    Transfer calls to a quick connect or external phone number using the Contact Control Panel (CCP) · Transfers create multiple contact records · Checked 2026-09-25
  3. 3
    After an agent initiates a transfer in the CCP, the customer is placed on hold and the agent is connected to the transfer destination.
  4. 4
    Once the transfer destination answers, the agent can choose Join to conference the caller, destination and agent, then choose Leave to complete the transfer and exit the call.
    Transfer calls to a quick connect or external phone number using the Contact Control Panel (CCP) · To transfer to a quick connect or to an external number, steps 3 and 4 · Checked 2026-09-25
  5. 5
    The documented Amazon Connect quick connect and CCP transfer features give no indication of a Teams user's availability before the agent dials, so presence-aware transfer to Teams users needs a custom Graph integration or a partner product.inferred
    Create quick connects in Connect Customer · More examples (external quick connects always shown); read with aws-connect-ccp-transfers procedure · Checked 2026-09-25
  6. 6
    In the CCP an agent on a contact can transfer to a quick connect, or choose Number pad, enter an external number and choose Call.
    Transfer calls to a quick connect or external phone number using the Contact Control Panel (CCP) · To transfer to a quick connect or to an external number, steps 1 and 2 · Checked 2026-09-25
  7. 7
    An agent-initiated transfer to a Teams user over the external voice transfer connector can be built as a queue quick connect whose Transfer to Queue flow contains the connector-targeted Transfer to phone number block, because phone number quick connects cannot carry a flow.inferred
    Flow block in Connect Customer: Transfer to phone number · Flow types (Transfer to Queue flow listed); combined with quick-connects More examples > Queue quick connects and external-voice-transfer flow block section · Checked 2026-09-25
  8. 8
    To send a call over an external voice transfer connector, the connector ARN is set as a contact attribute and a Transfer to phone number block in the flow uses that attribute as its destination.
    Set up Amazon Connect external voice transfer to an on-premise voice system · configure a Transfer flow block section (search-index text; page body not rendered) · Checked 2026-09-25
  9. 9
    When creating an external voice transfer connector, the Connector destination type identifies the device receiving calls from Amazon Connect, typically a Session Border Controller.
    Create external voice transfer connectors for Amazon Connect · connector details, Connector destination type (search-index text; page body not rendered) · Checked 2026-09-25
  10. 10
    An external voice transfer connector's Outbound routes section defines the route to the enterprise voice system by Host, Port, Protocol, Priority and Weight, with up to 10 routes.
    Create external voice transfer connectors for Amazon Connect · Outbound routes section (search-index text; page body not rendered) · Checked 2026-09-25
  11. 11
    External voice transfer connectors must first be enabled by a service quota increase for External voice transfer connectors per account; after approval External voice connectors appears in the Amazon Connect console.
    Set up Amazon Connect external voice transfer to an on-premise voice system · main steps list, step 1 (search-index text; page body not rendered) · Checked 2026-09-25
  12. 12
    The Graph get-presence API is available in the global service and US Government L4 and L5 (DoD) clouds but not in China operated by 21Vianet.
    Get presence - Microsoft Graph v1.0 · national cloud deployments table · Checked 2026-09-25
  13. 13
    Microsoft Graph returns a user's Teams presence (availability and activity) from GET /users/{id}/presence or /communications/presences/{id}, where {id} is the user's GUID.
    Get presence - Microsoft Graph v1.0 · HTTP Request and its Note; Examples response bodies · Checked 2026-09-25
  14. 14
    Reading another user's presence with application permissions needs Presence.Read.All as least privilege, and application permissions cannot use the /me path.
    Get presence - Microsoft Graph v1.0 · Permissions table and Note · Checked 2026-09-25
  15. 15
    The Graph get-presence API is limited to 1,500 requests per 30 seconds per application per tenant.
    Get presence - Microsoft Graph v1.0 · Permissions > Note, second bullet · Checked 2026-09-25
  16. 16
    CloudInteract's AWS Marketplace listing says its product transfers PSTN calls from Amazon Connect to Teams, shows agents the Teams status of transfer targets, and does not require Teams Phone licenses.
    Microsoft Teams Integration for Amazon Connect (CloudInteract) · listing overview · Checked 2026-09-25
  17. 17
    NeuraFlash's AWS Marketplace listing says its product shows colleagues' Teams availability in the Amazon Connect Agent Workspace, sets the agent's Teams status to Do Not Disturb during Connect calls, and supports transfer to Teams co-workers.
    NeuraFlash Teams Integration for Amazon Connect · listing overview · Checked 2026-09-25
  18. 18
    Direct Routing integrates a PSTN operator with the Teams tenant through a certified Session Border Controller procured and managed by the customer, an integrator or a Direct-Routing-as-a-Service provider.
    PSTN connectivity options · PSTN connectivity options > Direct Routing · Checked 2026-09-25
  19. 19
    Teams Phone connects to the PSTN through Microsoft Teams Calling Plan, Operator Connect, Teams Phone Mobile or Direct Routing, and a tenant can combine several of these.
    PSTN connectivity options · PSTN connectivity options; Use more than one PSTN connectivity type · Checked 2026-09-25
  20. 20
    To make and receive PSTN calls, a Teams user must be licensed for Teams Phone and also be equipped with a PSTN solution from a chosen provider.
    PSTN connectivity options · What is the Public Switched Telephone Network (PSTN)?, fourth paragraph · Checked 2026-09-25
  21. 21
    A quick connect becomes visible to agents in the CCP only after it is added to a queue, and agents see the quick connects of the queues in their routing profile including the default outbound queue.
    Create quick connects in Connect Customer · Step 2: Enable agents to see quick connects, and its Tip · Checked 2026-09-25
  22. 22
    While an agent invokes an agent, queue or external quick connect, the caller hears the Customer hold flow.
    Create quick connects in Connect Customer · More examples > External quick connects, final paragraph · Checked 2026-09-25
  23. 23
    When creating a phone number quick connect, the phone number is entered starting with the country code.
    Create quick connects in Connect Customer · Example: Create a phone number quick connect to a mobile phone, step 4 · Checked 2026-09-25
  24. 24
    External quick connects appear in the CCP at all times, whereas agent and queue quick connects appear only when the agent is on an active call.
    Create quick connects in Connect Customer · More examples (introductory paragraph) · Checked 2026-09-25
  25. 25
    External (phone number) quick connects invoke no flow, so the outbound caller ID cannot be set per transfer and is taken from the queue configuration.
    Create quick connects in Connect Customer · More examples > External quick connects · Checked 2026-09-25
  26. 26
    An Amazon Connect phone number quick connect transfers the contact to a phone number.
    Create quick connects in Connect Customer · Types of quick connects > Phone number quick connect · Checked 2026-09-25
  27. 27
    The queue that carries a phone number quick connect needs an Outbound caller ID number chosen from numbers claimed for the instance; AWS states this is required to make outbound calls.
    Create quick connects in Connect Customer · Example: Create a phone number quick connect to a mobile phone > Add the quick connect to a queue, step 2 · Checked 2026-09-25
  28. 28
    A queue quick connect invokes its associated Transfer to Queue flow when the agent selects it.
    Create quick connects in Connect Customer · More examples > Queue quick connects, step 2 · Checked 2026-09-25
  29. 29
    The SBC's Enabled setting turns it on for outbound calls and can be used to take the SBC temporarily out of service.
    Connect your Session Border Controller (SBC) to Direct Routing · SBC settings table, Enabled row · Checked 2026-09-25
  30. 30
    An SBC can be paired with Direct Routing only if the domain portion of its FQDN is registered in the tenant; *.onmicrosoft.com is not supported, and a user with that domain holding an E3 or E5 license must exist.
    Connect your Session Border Controller (SBC) to Direct Routing · Use PowerShell > Connect the SBC to the tenant > Considerations, second bullet · Checked 2026-09-25
  31. 31
    The SBC is paired with New-CsOnlinePSTNGateway using at minimum the FQDN, SipSignalingPort, MaxConcurrentSessions and Enabled parameters, or through Voice > Direct Routing > SBCs in the Teams admin center.
    Connect your Session Border Controller (SBC) to Direct Routing · Use the Microsoft Teams admin center; Use PowerShell > Connect the SBC to the tenant · Checked 2026-09-25
  32. 32
    Direct Routing enforces TLS 1.2 on its SIP interface, and the SBC must support one of four listed ECDHE-RSA AES cipher suites.
    Connect your Session Border Controller (SBC) to Direct Routing · Considerations, TLS1.2 bullet · Checked 2026-09-25
  33. 33
    SBC pairing is verified by confirming with Get-CsOnlinePSTNGateway that the SBC is listed with Enabled True, and on the SBC that its outgoing SIP OPTIONS receive 200 OK and it answers Direct Routing OPTIONS with 200 OK.
    Connect your Session Border Controller (SBC) to Direct Routing · Verify the SBC connection > Check whether the SBC is on the list of paired SBCs; Validate SIP options · Checked 2026-09-25
  34. 34
    A configured Transfer to phone number block has Success, Call Failed, Timeout and Error branches, and its timeout is configurable.
    Flow block in Connect Customer: Transfer to phone number · Configured block; Properties (Set timeout) · Checked 2026-09-25
  35. 35
    Outside the United States AWS recommends setting Caller ID number on the block to an Amazon Connect number, and in Australia and the UK carriers may reject calls whose caller ID does not meet local rules.
    Flow block in Connect Customer: Transfer to phone number · Properties > Caller ID recommendations for calls outside the US · Checked 2026-09-25
  36. 36
    When the Transfer to phone number block is used without a custom caller ID, the contact's own caller ID is presented to the external party.
    Flow block in Connect Customer: Transfer to phone number · Properties > Caller ID name, Note (final paragraph) · Checked 2026-09-25
  37. 37
    Transfers to a phone number in a country the instance is not allowlisted to call fail; allowlisting is requested through an Amazon Connect service quota increase.
    Flow block in Connect Customer: Transfer to phone number · Configuration tips, first and second bullets · Checked 2026-09-25
  38. 38
    The Transfer to phone number flow block supports only the voice channel and can be used in Inbound, Customer Queue, Transfer to Agent and Transfer to Queue flows.
    Flow block in Connect Customer: Transfer to phone number · Supported channels; Flow types · Checked 2026-09-25
  39. 39
    Resume flow after disconnect on the Transfer to phone number block returns the caller to the flow only if the external party disconnects; if the customer disconnects the whole call ends.
    Flow block in Connect Customer: Transfer to phone number · Properties > Resume flow after disconnect · Checked 2026-09-25
  40. 40
    A Direct Routing number is assigned with Set-CsPhoneNumberAssignment -PhoneNumber <number> -PhoneNumberType DirectRouting, which also enables Enterprise Voice; Microsoft recommends full E.164 format.
    Enable users for Direct Routing · Configure the phone number and enable enterprise voice > Use PowerShell · Checked 2026-09-25
  41. 41
    When users share a base number with unique extensions, the INVITE to Direct Routing must carry the full number with ;ext= for the user lookup to succeed.
    Enable users for Direct Routing · Configure the phone number and enable enterprise voice > Use PowerShell, final paragraph · Checked 2026-09-25
  42. 42
    Direct Routing requires users to be in Teams Only mode (UpgradeToTeams TeamsUpgradePolicy) so incoming calls land in the Teams client.
    Enable users for Direct Routing · Assign Teams Only mode to users to ensure calls land in Microsoft Teams · Checked 2026-09-25
  43. 43
    An SBC can send a Direct Routing call straight to a user's voicemail by appending opaque=app:voicemail to the Request-URI; the user gets no call notification.
    Enable users for Direct Routing · Configure sending calls directly to voicemail · Checked 2026-09-25
  44. 44
    Direct Routing outbound call routing is built from voice routing policies containing PSTN usages, which contain voice routes that map a called-number pattern to online PSTN gateways (SBCs).
    Configure call routing for Direct Routing · Call routing overview · Checked 2026-09-25
  45. 45
    Configuring the global online voice routing policy applies it to all voice-enabled users and can send Calling Plan and Operator Connect users' PSTN calls into a Direct Routing trunk; Microsoft advises custom policies assigned per user.
    Configure call routing for Direct Routing · Voice routing policy considerations > Caution, item 1 · Checked 2026-09-25
  46. 46
    When an incoming PSTN call is forwarded or transferred and the ingress SBC is also a possible egress SBC, Direct Routing ignores route priority and tries the ingress SBC first.
    Configure call routing for Direct Routing · Example 1: Voice routing with one PSTN usage, Note after the summary table · Checked 2026-09-25
  47. 47
    Phone number quick connects require only a phone number; a queue or flow cannot be set on them, and phone number transfers do not require a specific flow type.
    Set up contact transfers in Connect Customer · Overview of steps, steps 1 and 3 · Checked 2026-09-25
  48. 48
    For agents to transfer, the queue holding the quick connect must be in a routing profile assigned to those agents.
    Set up contact transfers in Connect Customer · Overview of steps, step 5 · Checked 2026-09-25
  49. 49
    Firewall and SBC settings must accept connections from any Microsoft signaling IP address because a REFER can arrive on a new TLS connection from a different address.
    Issues with call transfers - Microsoft Teams · No SIP REFER received by the SBC from the SIP proxy, step 2 · Checked 2026-09-25
  50. 50
    Since a June 2026 change (Message Center MC1296872), Microsoft ends a blind-transferred Direct Routing call as soon as the SBC accepts the REFER, without waiting for the transfer result.
    Issues with call transfers - Microsoft Teams · Calls drop before the transfer is completed, final paragraph · Checked 2026-09-25
  51. 51
    For consultative transfers the SBC must return 202 Accepted and NOTIFY progress to the REFER; the proxy ends the original call only after a NOTIFY carrying 200 OK.
    Issues with call transfers - Microsoft Teams · Calls drop before the transfer is completed · Checked 2026-09-25
  52. 52
    On a Teams REFER the SBC must send the new INVITE back to the Microsoft SIP proxy, with the Request-URI set to the Refer-To string and the Referred-By header copied unchanged, even when the target is an external PSTN number.
    Issues with call transfers - Microsoft Teams · Call transfer methods, second numbered list, items 2 to 5 · Checked 2026-09-25
  53. 53
    Teams initiates Direct Routing transfers by SIP REFER first, then INVITE with Replaces, then an internal method invisible to the SBC if neither is supported.
    Issues with call transfers - Microsoft Teams · Call transfer methods, numbered list · Checked 2026-09-25
  54. 54
    Microsoft's Direct Routing call-transfer troubleshooting guidance does not apply to Calling Plan or Operator Connect deployments.
    Issues with call transfers - Microsoft Teams · opening Note · Checked 2026-09-25
  55. 55
    An Amazon Connect instance needs a claimed DID or toll-free phone number to place or receive calls.
    Get a local toll-free or DID Connect Customer phone number · Get a local toll-free or DID Connect Customer phone number (opening paragraph) · Checked 2026-09-25
  56. 56
    By default an Amazon Connect account can claim and release up to 200% of its phone-number quota in a rolling 180-day period; exceeding that blocks further claims until an AWS support case is opened or the period expires.
    Get a local toll-free or DID Connect Customer phone number · Avoid being blocked from claiming or releasing too many numbers · Checked 2026-09-25
  57. 57
    An Amazon Connect phone number cannot be claimed again after it is released.
    Get a local toll-free or DID Connect Customer phone number · How many phone numbers you can claim · Checked 2026-09-25
  58. 58
    Amazon Connect requires phone numbers in E.164 format, for example +18005551212 for a US number.
    Set up outbound caller ID in Connect Customer · Use E.164 format for international phone numbers · Checked 2026-09-25
  59. 59
    An SBC is paired with New-CsOnlinePSTNGateway (Fqdn, SipSignalingPort, Enabled), and Get-CsOnlinePSTNGateway should then list it with Enabled True; the module also provides Set-CsOnlinePSTNGateway and Remove-CsOnlinePSTNGateway, and setting Enabled to False temporarily removes an SBC from service.
    Connect your Session Border Controller (SBC) to Direct Routing · Connect the SBC to the tenant; Verify the SBC connection · Checked 2026-09-25
  60. 60
    Only numbers claimed or ported to Amazon Connect can be the outbound caller ID number unless AWS Support activates an external number for custom caller ID after proof of ownership.
    Set up outbound caller ID in Connect Customer · Outbound parameters: Set in queue > Outbound caller ID number · Checked 2026-09-25
  61. 61
    The CCP shows Invalid outbound configuration when outbound calling is not enabled on the instance or the queue has no outbound caller ID; agents also need the CCP - Make outbound calls permission.
    Contact Control Panel (CCP) Issues · CCP outbound configuration issues > How to fix · Checked 2026-09-25
  62. 62
    An Amazon Connect external voice connector is billed at $100 per connector per day (US West (Oregon) rate).
    Amazon Connect Customer Pricing Appendix · External voice > External voice connector · Checked 2026-09-25
  63. 63
    For a transfer made while the agent is on a call, caller ID comes from the inbound queue that handled the call and the outbound whisper flow cannot override it; to control it, use a Transfer to phone number block with an explicit caller ID.
    Set up outbound caller ID in Connect Customer · How outbound parameters are selected > Note · Checked 2026-09-25
  64. 64
    An external transfer from Amazon Connect stays anchored to the instance's Region for the whole call: per-minute usage accrues until the transfer recipient hangs up, and the call is not recorded after the agent drops or the transfer completes.
    Set up your network to use the Connect Customer Contact Control Panel (CCP) · Region selection considerations > External transfers · Checked 2026-09-25
  65. 65
    AWS advises against transferring calls to destinations that could transfer them back into Amazon Connect (circular transfers), because PSTN latency compounds.
    Set up your network to use the Connect Customer Contact Control Panel (CCP) · Region selection considerations > External transfers (last sentence) · Checked 2026-09-25

Documents

tier 2 current vendor documentation

Amazon Connect Customer Pricing Appendix

Amazon Web Services · accessed 2026-09-25

tier 2 current vendor documentation

Configure call routing for Direct Routing

Microsoft · 2026-09-10 · accessed 2026-09-21

tier 2 current vendor documentation

Configure your external voice system for integration with conversational analytics

Amazon Web Services · accessed 2026-09-25

tier 2 current vendor documentation

Connect your Session Border Controller (SBC) to Direct Routing

Microsoft · 2026-04-26 · accessed 2026-09-21

tier 2 current vendor documentation

Contact Control Panel (CCP) Issues

Amazon Web Services · accessed 2026-09-25

tier 2 current vendor documentation

Create external voice transfer connectors for Amazon Connect

Amazon Web Services · accessed 2026-09-25

tier 2 current vendor documentation

Create quick connects in Connect Customer

Amazon Web Services · accessed 2026-09-25

tier 2 current vendor documentation

Enable users for Direct Routing

Microsoft · 2026-08-21 · accessed 2026-09-21

tier 2 current vendor documentation

Flow block in Connect Customer: Transfer to phone number

Amazon Web Services · accessed 2026-09-25

tier 2 current vendor documentation

Get a local toll-free or DID Connect Customer phone number

Amazon Web Services · accessed 2026-09-25

tier 2 current vendor documentation

Get presence - Microsoft Graph v1.0

Microsoft · 2024-04-04 · accessed 2026-09-25

tier 2 current vendor documentation

Issues with call transfers - Microsoft Teams

Microsoft · 2026-08-31 · accessed 2026-09-25

tier 2 current vendor documentation

PSTN connectivity options

Microsoft (Microsoft Learn) · 2026-08-06 · accessed 2026-09-06

tier 2 current vendor documentation

Set up Amazon Connect external voice transfer to an on-premise voice system

Amazon Web Services · accessed 2026-09-25

tier 2 current vendor documentation

Set up contact transfers in Connect Customer

Amazon Web Services · accessed 2026-09-07

tier 2 current vendor documentation

Set up outbound caller ID in Connect Customer

Amazon Web Services · accessed 2026-09-25

tier 2 current vendor documentation

Set up your network to use the Connect Customer Contact Control Panel (CCP)

Amazon Web Services · accessed 2026-09-24

tier 2 current vendor documentation

Transfer calls to a quick connect or external phone number using the Contact Control Panel (CCP)

Amazon Web Services · accessed 2026-09-25

tier 3 vendor-maintained repositories

Microsoft Teams Integration for Amazon Connect (CloudInteract)

CloudInteract via AWS Marketplace · accessed 2026-09-25

tier 3 vendor-maintained repositories

NeuraFlash Teams Integration for Amazon Connect

NeuraFlash via AWS Marketplace · accessed 2026-09-25

Cite this page

APA

WarmTransfer. (2026, September 25). Microsoft Teams with Amazon Connect. WarmTransfer. https://warmtransfer.net/guides/teams-with-amazon-connect

BibTeX

@misc{warmtransfer-teams-with-amazon-connect,
  title  = {Microsoft Teams with Amazon Connect},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/guides/teams-with-amazon-connect},
  note   = {Verified 2026-09-25}
}