Merge pull request #2627 from MicrosoftDocs/repo_sync_working_branch

Resolve syncing conflicts from repo_sync_working_branch to main

.openpublishing.redirection.json

@@ -975,6 +975,11 @@
       "source_path": "power-platform/admin/storage-sas-token.md",
       "redirect_url": "/power-platform/admin/access-storage",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "power-platform/admin/onpremises-data-gateway-source-management.md",
+      "redirect_url": "/power-platform/admin/wp-onpremises-gateway",
+      "redirect_document_id": false
     }
   ]
 }

power-platform/admin/TOC.yml

@@ -814,7 +814,7 @@
                               href: create-dataverseapplicationuser.md
                         - name: Tenant Settings
                           items:
-                            - name: "List tenant settings"
+                            - name: List tenant settings (preview)
                               href: list-tenantsettings.md
         - name: Data integration
           items:
@@ -852,6 +852,8 @@
               href: run-bulk-system-jobs-detect-duplicate-records.md
             - name: Bulk deletion
               href: delete-bulk-records.md
+            - name: Set address record settings
+              href: disable-delete-address-records.md
             - name: View and take action on bulk deletion jobs
               href: view-take-action-bulk-deletion-jobs.md
             - name: Restore deleted table records (preview)

power-platform/admin/configure-relevance-search-organization.md

@@ -4,7 +4,7 @@ description: Configure Dataverse search to improve search results and performanc
 author: sericks007
 ms.component: pa-admin
 ms.topic: conceptual
-ms.date: 05/16/2024
+ms.date: 05/17/2024
 ms.subservice: admin
 ms.author: sericks
 search.audienceType: 
@@ -14,7 +14,7 @@ contributors:
 ---
 # Configure Dataverse search for your environment
 
-Dataverse search delivers fast and comprehensive search results in a single list, sorted by relevance. As an administrator or customizer, you can enable and configure Dataverse search as described in this article. Quick Find views are used for configuring Dataverse search, so you can manage global search, quick find, and lookup search behavior in one single place.
+Dataverse search delivers fast and comprehensive search results in a single list, sorted by [relevance](/azure/search/index-similarity-and-scoring). As an administrator or customizer, you can turn on and configure Dataverse search as described in this article. Quick Find views are used for configuring Dataverse search, so you can manage global search, quick find, and lookup search behavior in one single place.
 
 With Dataverse search enabled, a search box is always available at the top of every page in all the model-driven apps in the **environment**. Once Dataverse search is enabled, it applies to all apps and can't be disabled per app. Users can start a new search and quickly find the information they're looking for, from the searchable tables included in the app. Dataverse search also becomes the default and only global search experience in all model-driven apps in the environment. Users won't be able to switch to [quick find search](/powerapps/user/quick-find) formerly known as categorized search.  
 
@@ -119,6 +119,8 @@ Setting up Dataverse search after enabling it in the **Power Platform admin cent
 
 3. Ensure the tables enabled for Dataverse search are included in the model-driven app. Use the app designer to verify that the table is included in an app's components. For more information, see [Add or edit model-driven app components](/powerapps/maker/model-driven-apps/add-edit-app-components#add-a-component).
 
+4. Make sure your table is customizable and that the settings to **Track changes** and **Appear in search results** in the **Advanced options** are both set to **On**. For more information, see [Create and edit tables using Power Apps](/power-apps/maker/data-platform/create-edit-entities-portal?tabs=excel).
+
 ### Select tables for Dataverse search
 
 Setting up search starts with reviewing the tables that are enabled for Dataverse search, in context of a solution. Using the new solution explorer, you can see a snapshot of the Dataverse search index on the **Overview** page.

power-platform/admin/create-users.md

@@ -82,29 +82,29 @@ The following table shows the fields that are managed in the **Users** section o
 <table>
 <thead>
 <tr class="header">
-<th><p>Customer engagement apps user form </th><th>Microsoft 365/Microsoft Entra user</th></tr>
+<th><p>Customer engagement apps user form </th><th>Dataverse SystemUser object</th><th>Microsoft 365/Microsoft Entra user</th></tr>
 </thead>
 <tbody>
-<tr><td>User Name</td><td>Username</td></tr>
-<tr><td>Full Name*  </td><td>Display Name </td></tr>
-<tr><td>Title </td><td>Job title </td></tr>
- <tr><td>First Name </td><td>First Name </td></tr>
- <tr><td>Last Name </td><td>Last Name </td></tr>
-<tr><td>Primary Email** </td><td>Email </td></tr>
-<tr><td>InternalEmailAddress*** </td><td>Mail </td></tr>
-<tr><td>Main Phone </td><td>Office phone</td></tr>
-<tr><td>Mobile Phone  </td><td>Mobile phone</td></tr>
-<tr><td>Address  </td><td>Street address   </td></tr>
-<tr><td>Address   </td><td>City   </td></tr>
-<tr><td>Address   </td><td>State or province    </td></tr>
-<tr><td>Address    </td><td>Country or region    </td></tr>
-<tr><td>AzureActiveDirectoryObjectId****     </td><td>ObjectId   </td></tr>
-<tr><td colspan="2">* Full Name isn't automatically updated and synchronized with customer engagement apps.<br>** To prevent data loss, the Primary Email field isn't automatically updated and synchronized with customer engagement apps.<br>***InternalEmailAddress can be updated by customers; after which, sync will no longer update this field.<br>**** ObjectID of a user or a service principal in Microsoft Entra ID.<br /></td></tr>
+<tr><td>User Name</td><td>DomainName</td><td>Username</td></tr>
+<tr><td>Full Name*  </td><td>Full Name </td><td>Full Name </td></tr>
+<tr><td>Title </td><td>JobTitle </td><td>Job title </td></tr>
+<tr><td>First Name </td><td>FirstName </td><td>First Name </td></tr>
+<tr><td>Last Name </td><td>LastName </td><td>Last Name </td></tr>
+<tr><td>Primary Email**</td><td>InternalEmailAddress***</td><td>Mail </td></tr>
+<tr><td>Main Phone </td><td>Address1_Telephone1 </td><td>Office phone</td></tr>
+<tr><td>Mobile Phone  </td><td>MobilePhone  </td><td>Mobile phone</td></tr>
+<tr><td>Street  </td><td>Address1_Line1   </td><td>Street address   </td></tr>
+<tr><td>City  </td><td>Address1_City   </td><td>City   </td></tr>
+<tr><td>State/Province   </td><td>Address1_StateOrProvince    </td><td>State or province    </td></tr>
+<tr><td>Postal Code   </td><td>Address1_PostalCode    </td><td>Postal Code    </td></tr>
+<tr><td>Country   </td><td>Address1_Country    </td><td>Country or region    </td></tr>
+<tr><td>AzureActiveDirectoryObjectId****     </td><td>AzureActiveDirectoryObjectId   </td><td>ObjectId   </td></tr>
+<tr><td colspan="3">* Full Name isn't automatically updated and synchronized with customer engagement apps.<br>** To prevent data loss, the PrimaryEmail field isn't automatically updated and synchronized with customer engagement apps.<br>***InternalEmailAddress can be updated by customers; after which, sync will no longer update this field.<br>**** ObjectID of a user or a service principal in Microsoft Entra ID.<br /></td></tr>
 </tbody>
 </table>
 
 > [!NOTE]
-> Custom fields are **never** synchronized between Microsoft 365, Microsoft Entra ID, and Power Platform.
+> Custom fields are **never** synchronized between Microsoft 365, Microsoft Entra, and Power Platform.
 > 
 > All the fields are **always** synchronized, except fields explicitly mentioned as not automatically updated (custom fields, Full Name, Primary Email, and Internal Email Address after a customer update).
 >

power-platform/admin/disable-delete-address-records.md

@@ -0,0 +1,53 @@
+---
+title: Set address record settings
+description: Learn how to prevent empty address records from being created and how to allow users to delete address data.
+author: mkannapiran 
+ms.component: pa-admin
+ms.topic: conceptual
+ms.date: 05/17/2024
+ms.subservice: admin
+ms.author: kamanick
+ms.reviewer: sericks
+search.audienceType: 
+  - admin
+---
+
+# Set address record settings
+
+This article explains how to prevent empty address records from being created and how to allow users to delete address data.
+
+## Prevent empty address records from being created
+
+The **Disable empty address record creation** setting helps you prevent address record creation in Dataverse when there's no data in the address segment of a payload. This feature only supports **Account** and **Contact** tables in Dataverse. Any other table that is associated with an address isn't impacted by this setting.
+
+For example, suppose there's an incoming payload for the **Account** table and the address data is empty. If the **Disable empty address record creation** setting is set to **On**, it prevents an empty record from being created in Dataverse. However, if the same payload contains address data, then an address record is created in Dataverse.
+
+> [!Note]
+> Turning on the **Disable empty address record creation** setting doesn't remove existing empty address records.
+
+Complete the following steps to prevent empty address records from being created.
+
+1. Sign in to the [Power Platform admin center](https://admin.powerplatform.microsoft.com).
+1. Select **Environments** in the navigation pane.
+1. Select the checkmark next to an environment, and then select **Settings** in the command bar.
+1. Select **Product** > **Features**.
+1. Find the **Disable Empty Address Record Creation** setting and turn it **On**.
+1. Select **Save** on the bottom of the page to save the changes.
+
+## Allow users to delete address data
+
+The **Enable deletion of address records** setting allows a user to delete address data in Dataverse. The default setting for this setting is **Off**, which means that users can't delete address records in Dataverse. The address record deletion capability is applicable only for **Account** and **Contact** tables in Dataverse.
+
+Turning on the **Enable deletion of address records** setting allows address records to be deleted in the following ways:
+- Through the user experience in Power Platform.
+- Through bulk delete operations
+- Through SDK.
+
+Complete the following steps to allow users to delete address data.
+
+1. Sign in to the [Power Platform admin center](https://admin.powerplatform.microsoft.com).
+1. Select **Environments** in the navigation pane.
+1. Select the checkmark next to an environment, and then select **Settings** in the command bar.
+1. Select **Product** > **Features**.
+1. Find the **Enable deletion of address records** setting and turn it **On**.
+1. Select **Save** on the bottom of the page to save the changes.

power-platform/admin/list-tenantsettings.md

@@ -5,12 +5,13 @@ author: laneswenka
 ms.reviewer: sericks
 ms.component: pa-admin
 ms.topic: reference
-ms.date: 04/23/2024
+ms.date: 05/17/2024
 ms.subservice: admin
 ms.author: laswenka
 search.audienceType: 
   - admin
 contributors:
+- arjunmayur 
 - bibekTimalsina948
 - dannylevymsft
 ms.collection: bap-ai-copilot
@@ -77,7 +78,7 @@ The response is always a **200 OK** response, unless you aren't correctly authen
             "shareWithColleaguesUserLimit": 10000
         },
         "powerApps": {
-            "disableShareWithEveryone": false,
+            "disableShareWithEveryone": true,
             "enableGuestsToMake": false
         },
         "modelExperimentation": {
@@ -106,9 +107,8 @@ The response is always a **200 OK** response, unless you aren't correctly authen
 |powerPlatform.search.disableDocsSearch | Boolean | When this setting is true, users in the environment can see a message that indicates Microsoft Learn and documentation search categories have been turned off by the administrator. Default value is false.|
 |powerPlatform.search.disableCommunitySearch | Boolean | When this setting is true, users in the environment can see a message that indicates community and blog search categories have been turned off by the administrator. Default value is false.|
 |powerPlatform.search.disableBingVideoSearch | Boolean | When this setting is true, users in the environment can see a message that indicates video search categories have been turned off by the administrator. Default value is false.|
-|powerPlatform.powerApps.disableShareWithEveryone | Boolean | Ability to disable the **Share with Everyone** capability for nonadmin users in all Power Apps. Default value is false.|
+|powerPlatform.powerApps.disableShareWithEveryone | Boolean | Ability to turn off the **Share with Everyone** capability for nonadmin users in all Power Apps. Default value is true.|
 |powerPlatform.teamsIntegration.shareWithColleaguesUserLimit | Integer | Maximum value setting for the number of users in a security group used to share an app built using Power Apps on Microsoft Teams. Default value is 10000 but can be increased or decreased, as required.|
-|powerPlatform.powerApps.disableShareWithEveryone | Boolean | Ability to disable the **Share with Everyone** capability in all Power Apps. Default value is false.|
 |powerPlatform.powerApps.DisableConnectionSharingWithEveryone | Boolean | Gets or sets a value indicating whether non-admin users in the tenant can share connections with everyone. Default value is false. |
 |powerPlatform.powerApps.enableGuestsToMake | Boolean | Ability to allow guest users in your tenant to create Power Apps. Default value is false.|
 |powerPlatform.powerApps.disableMembersIndicator | Boolean | This setting isn't currently used by the platform but might be used in the future.|