Merge pull request #4127 from MicrosoftDocs/main

master into temp

Author: jimholtz

.acrolinx-config.edn

@@ -1,4 +1,4 @@
-{:allowed-branchname-matches ["^master$", "demo-master-3"]
+{:allowed-branchname-matches ["^main$"]
  :allowed-filename-matches ["power-platform" "power-virtual-agents"]
  :use-skip-label true
  :targets

.openpublishing.publish.config.json

@@ -49,13 +49,13 @@
     {
       "path_to_root": "_themes",
       "url": "https://github.com/Microsoft/templates.docs.msft",
-      "branch": "master",
+      "branch": "main",
       "branch_mapping": {}
     },
     {
       "path_to_root": "_themes.pdf",
       "url": "https://github.com/Microsoft/templates.docs.msft.pdf",
-      "branch": "master",
+      "branch": "main",
       "branch_mapping": {}
     }
   ],
@@ -64,7 +64,7 @@
       "Publish",
       "Pdf"
     ],
-    "master": [
+    "main": [
       "Publish",
       "Pdf"
     ],

power-platform/admin/OrgDbOrgSettings.md

@@ -5,7 +5,7 @@ author: mduelae
 ms.service: power-platform
 ms.component: pa-admin
 ms.topic: conceptual
-ms.date: 08/25/2021
+ms.date: 11/18/2021
 ms.subservice: admin
 ms.author: mkaur
 search.audienceType: 
@@ -26,7 +26,7 @@ This topic covers the default values of OrgDBOrgSettings that are specific to se
 | AutoCreateContactOnPromote | true | Disables the ability to automatically create a contact row for unresolved senders on promotion of an email. <br> This option is organization-wide, but can also be disabled from the personal options setting for each user. More information: [Set personal options](/powerapps/user/set-personal-options#email-tab-options) |
 | SSSUpdatePastMeetingsInNonDraftMode | false | Allows updates for meetings set entirely within the past in Dynamics 365 to be propagated to Exchange when properties such as start, end, subject, body, attendees, or location are changed. <br>**Note**: If this setting is enabled, Exchange will send out meeting invites, updates, and cancellations for past meetings synchronized from Dynamics 365. |
 | DoNotIgnoreInternalEmailToQueues | true | If **Track emails sent between Dynamics 365 users as two activities** is disabled in [system settings](settings-email-tracking.md), this setting allows emails sent from a user to a queue mailbox to be synchronized to Dynamics 365 if the queue's incoming email delivery settings would otherwise accept the email. |
-| CreateQueueItemForSynchronizingMailbox | false | Allows queue items to be created for a synchronized mailbox when there's no recipient in the **To:** or **Cc:** field. <br> More information: [Create queue items from synchronized email messages](create-queue-items-from-synchronized-email-messages.md) |
+| CreateQueueItemForSynchronizingMailbox | true | Allows queue items to be created for a synchronized mailbox when there's no recipient in the **To:** or **Cc:** field. <br> More information: [Create queue items from synchronized email messages](create-queue-items-from-synchronized-email-messages.md) |
 | UsePlainTextForEmailTemplateBody | false | Changes the email template to use plain text where otherwise text with the following symbols wouldn't appear: &lt;text&gt;. |
 | EmailTemplateRetrieveFallbackContact | false | When referencing a contact on a lead or opportunity in an email template, use fallback logic to pick up a fallback contact such as primarycontactid or parentcontactId when the referenced contact is empty. |
 | ResolveForInactiveEntities | false | When enabled, email addresses for inactive tables are ignored for email address resolution. <br> **Note**: This setting doesn't apply to system users whose accounts have been disabled, who are always excluded. |

power-platform/admin/create-queue-items-from-synchronized-email-messages.md

@@ -1,7 +1,7 @@
 ---
 title: "Create queue items from synchronized email messages | MicrosoftDocs"
 description: Provides information about creating queue items from synchronized email messages.
-ms.date: 02/03/2021
+ms.date: 11/18/2021
 ms.service: power-platform
 ms.topic: "article"
 author: mduelae
@@ -21,7 +21,7 @@ search.app:
 There are several OrgDbOrgSetting options available to control how queue items are automatically created for synchronized email. If you are unfamiliar with OrgDbOrgSettings, see the [KB article](https://support.microsoft.com/topic/orgdborgsettings-tool-for-microsoft-dynamics-crm-20a10f46-2a24-a156-7144-365d49b842ba). Note that the following settings are applied to the entire organization.
 
 - **CreateQueueItemForSynchronizingMailbox**
-  - When enabled, the system will add the currently synchronizing queue mailbox to the list of queues for which to create a queue item. Consider enabling this option if queue mailboxes potentially receive or process email in which they are not in the recipient list, such as through distribution list memberships or as BCC recipients.  The default value is false.
+  - When enabled, the system will add the currently synchronizing queue mailbox to the list of queues for which to create a queue item. Consider enabling this option if queue mailboxes potentially receive or process email in which they are not in the recipient list, such as through distribution list memberships or as BCC recipients.  The default value is true.
 - **CreateQueueItemsForAcceptingQueueRecipients**
   - When enabled, the system will create a queue item for each resolved queue recipient during incoming email processing. If **AutoRouteToOwnerQueue** is enabled for the email table, the system additionally creates a queue item in the email owner’s default queue.  The default value is true.
 - **SSSCreateAdditionalQueueItemsForAlreadyTrackedEmail**
@@ -40,4 +40,4 @@ These settings can be mixed and matched to achieve the desired flexibility in ho
 5. Step 4 can repeat as needed as more queues ‘opt-in’ to the queue item creation process by moving the email to the inbox folder for processing.
 
 
-[!INCLUDE[footer-include](../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../includes/footer-banner.md)]

power-platform/admin/data-integrator-error-management.md

@@ -4,7 +4,7 @@ description: "Troubleshoot issues and manage errors when executing data integrat
 ms.service: power-platform
 ms.topic: how-to
 ms.component: cds
-ms.date: 02/04/2021
+ms.date: 11/19/2021
 author: sabinn-msft
 ms.subservice: admin
 ms.author: sabinn
@@ -23,6 +23,21 @@ The Data Integrator is a point-to-point integration service used to integrate da
 
 While we are constantly evolving and driving fixes into the platform based on customer feedback, we understand there is a need to provide guidance when you run into issues. This topic walks you through error management and troubleshooting some of these issues.
 
+## Supported regions
+
+The Data Integrator is supported for the following regions:
+- Asia
+- Australia
+- Canada
+- Europe
+- India
+- Japan
+- South America
+- United Kingdom
+- United States
+
+There are no plans to enable Data Integrator for any other region.
+
 ## View health of project executions
 
 Every time a data integration project is executed (manually or scheduled), you can view the status of the execution on the admin dashboard and/or the project list page.  
@@ -198,4 +213,4 @@ Additionally, you can open the job history of the project and drill through the
 
 
 
-[!INCLUDE[footer-include](../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../includes/footer-banner.md)]

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

@@ -35,7 +35,7 @@ For more information about hand off, and how to use hand-off within a bot conver
 * Environments:
   * You must install the [extension solutions](#install-extension-solutions) in the same environment where you have your bots.
   - Your bot (and extension solutions) environment and omnichannel environment must be in the same [geographical region](data-location.md#data-locations).
-  - 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).
+  - For voice-based capabilities, both your tenant _and_ environment must be in the [United States Azure geographic location](data-location.md#data-locations).
 * 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).
 * 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.
 * 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.