Skip to content

Commit 11f907c

Browse files
authored
Merge pull request #4115 from MicrosoftDocs/master
[PVA] to live (tenant fix)
2 parents 43b2cb3 + ec031ba commit 11f907c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

power-virtual-agents/configuration-hand-off-omnichannel.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ For more information about hand off, and how to use hand-off within a bot conver
3535
* Environments:
3636
* You must install the [extension solutions](#install-extension-solutions) in the same environment where you have your bots.
3737
- Your bot (and extension solutions) environment and omnichannel environment must be in the same [geographical region](data-location.md#data-locations).
38-
- For voice-based hand off capabilities, your environments must be hosted in a datacenter within the [United States Azure geographic location](data-location.md#data-locations).
38+
- For voice-based capabilities, both your tenant _and_ environment must be in the [United States Azure geographic location](data-location.md#data-locations).
3939
* You need a [product license for Power Virtual Agents](https://go.microsoft.com/fwlink/?LinkId=2092080&clcid=0x409) and a [product license with the Chat Add-in for Dynamics 365 Customer service](/dynamics365/customer-engagement/omnichannel/try-chat-for-dynamics365).
4040
* You must be [assigned the omnichannel administrator role](/dynamics365/omnichannel/administrator/add-users-assign-roles#understand-roles-and-their-privileges) to connect bots with omnichannel.
4141
* You'll need an [application registered in Azure](/azure/active-directory/develop/howto-create-service-principal-portal#create-an-azure-active-directory-application) before you can connect to omnichannel.

0 commit comments

Comments
 (0)