Merge pull request #8385 from MicrosoftDocs/main

Merge main to live

Author: phecke

powerapps-docs/developer/data-platform/register-plug-in.md

@@ -206,7 +206,7 @@ Similarly, you should note that removing the assembly from the solution won't re
 
 ### Set user impersonation for a step
 
-With the Plug-in Registration tool running and logged into the target Dataverse environment, you can proceed to set or change a step registration. In this section, we will discuss changing the user on whos behalf the plug-in will perform its operations. Meaning, the effective user that is performing the data operations initiated by the plug-in. By default, the calling user (the user that invoked an operation in Dataverse) is the owner of said operations. However a different user can be specified in the step registration. You will need to have the System Administrator or System Customizer security role to perform this operation.
+With the [Plug-in Registration tool](#about-the-plug-in-registration-tool) running and logged into the target Dataverse environment, you can proceed to set or change a step registration. In this section, we will discuss changing the user on whos behalf the plug-in will perform its operations. Meaning, the effective user that is performing the data operations initiated by the plug-in. By default, the calling user (the user that invoked an operation in Dataverse) is the owner of said operations. However a different user can be specified in the step registration. You will need to have the System Administrator or System Customizer security role to perform this operation.
 
 To set the user in a plug-in step:
 
@@ -244,7 +244,7 @@ You can unregister or disable plug-ins and their components using the Plug-in Re
 
 ### Disable or enable a plug-in step
 
-With the Plug-in Registration tool running and logged into the target Dataverse environment, you can proceed to disable or enable plug-in steps. Disabling a step effectively turns off the plug-in from executing when Dataverse processes the entity and message combination specified in the step registration.
+With the [Plug-in Registration tool](#about-the-plug-in-registration-tool) running and logged into the target Dataverse environment, you can proceed to disable or enable plug-in steps. Disabling a step effectively turns off the plug-in from executing when Dataverse processes the entity and message combination specified in the step registration.
 
 > [!IMPORTANT]
 > Disabling a plug-in can negatively affect the functionality of your app, a solution, or the Dataverse system. Make sure you understand the implications before you proceed.

powerapps-docs/developer/data-platform/scalable-customization-design/database-transactions.md

@@ -31,8 +31,6 @@ One of the most fundamental concepts behind many of the challenges faced here is
 A common reason that problems can occur in this area is the lack of awareness of how customizations can affect transactions.
 
 Although the details of how this is done is beyond the scope of this topic, the most simple element to consider is that as Dataverse interacts with data in its database. SQL Server determines the appropriate locks to be taken by transactions on that data such as:
-- When retrieving a particular record, SQL Server takes a read lock on that record.
-- When retrieving a range of records, in some scenarios it can take a read lock on that range of records or the entire table.
 - When creating a record, it generates a write lock against that record.
 - When updating a record, it takes a write lock against the record.
 - When a lock is taken against a table or record, it’s also taken against any corresponding index records.

powerapps-docs/developer/model-driven-apps/clientapi/send-in-app-notifications.md

@@ -1,7 +1,7 @@
 ---
 title: "Send in-app notifications within model-driven apps" 
 description: Learn how to configure notifications in model-driven apps by using a client API.
-ms.date: 05/22/2023
+ms.date: 06/23/2023
 ms.reviewer: jdaly
 ms.service: powerapps
 ms.subservice: mda-developer
@@ -20,13 +20,13 @@ contributors:
 
 Developers of model-driven apps can configure notifications to be displayed to app users as a toast or within the notification center. Your model-driven app automatically polls the system for new notifications and displays them to the user. The notification sender or your system administrator can configure how the notification is shown and how it can be dismissed. Notifications appear in the notification center until the recipient dismisses them or they expire. By default, a notification expires after 14 days but your administrator can override this setting.
 
-Notifications are user-specific. Each notification is intended for a single user, identified as the recipient when the notification is sent. If a notification needs to be sent to multiple users, individual notifications must be created and sent for each recipient.
+Notifications are user-specific. Each notification is intended for a single user, identified as the recipient when the notification is sent. Sending a notification to a team isn't supported. If you need to send notifications to multiple users, you must create notifications for each individual user.
 
 This article outlines the steps for how to send in-app notifications to a specific user. To see how these notifications appear in applications, see [In-app notifications in model-driven apps](/powerapps/user/notifications).
 
 ## Enable the in-app notification feature
 
-To use the in-app notification feature, you need to enable the **In-app notifications** setting.  This setting is stored within the model-driven app.
+To use the in-app notification feature, you need to enable the **In-app notifications** setting. This setting is stored within the model-driven app.
 
 1. Sign in to [Power Apps](https://make.powerapps.com).
 
@@ -36,7 +36,7 @@ To use the in-app notification feature, you need to enable the **In-app notifica
 
 1. Open **Settings** and switch to **Features**.
 
-1. Enable "In-app notifications".
+1. Enable **In-app notifications**.
 
     > [!div class="mx-imgBorder"]
     > ![Custom page as main page](media/send-in-app-notifications/app-designer-settings-enable-in-app-notifications.png "Custom page as main page")
@@ -162,7 +162,7 @@ Notifications sent using the `SendAppNotification` message are stored in the [No
 |Display Name|Schema Name|Description|
 |---|---|---|
 |**Title**|`Title`|The title of the notification.|
-|**Owner**|`OwnerId`|The user who receives the notification.|
+|**Owner**|`OwnerId`|The *user* who receives the notification. While this column can be set to either a user or team, you must only set this to a user. The notification can't be set to a team.|
 |**Body**|`Body`|Details about the notification.|
 |IconType|`IconType`|The list of predefined icons. The default value is `Info`. For more information, go to [Changing the notification icon](#changing-the-notification-icon) later in this article.|
 |**Toast Type**|`ToastType`|The list of notification behaviors. The default value is `Timed`. For more information, go to [Changing the notification behavior](#changing-the-notification-behavior) later in this article.|
@@ -1143,4 +1143,4 @@ The Power Apps Notification connector is for push notifications, which are separ
 [createRecord (Client API reference)](reference/xrm-webapi/createrecord.md)<br />
 [In-app notifications in model-driven apps](/powerapps/user/notifications)<br />
 [appnotification EntityType](/power-apps/developer/data-platform/webapi/reference/appnotification)<br />
-[Notification (appnotification) table/entity reference](../../data-platform/reference/entities/appnotification.md)
+[Notification (appnotification) table/entity reference](../../data-platform/reference/entities/appnotification.md)

powerapps-docs/maker/canvas-apps/connections-list.md

@@ -15,6 +15,7 @@ contributors:
   - lancedMicrosoft
   - mduelae
   - alaug
+  - ProfessorKendrick
 ---
 # Overview of connectors for canvas apps
 
@@ -24,7 +25,7 @@ A connector may provide **tables** of data or **actions**. Some connectors provi
 
 ## Tables
 
-If your connector provides tables, you add your data source and then select the table in the data source that you want to manage. Power Apps both retrieves table data into your app and updates data in your data source automatically for you. For example, you can add a data source that contains a table named **Lessons** and then set the **Items** property of a control, such as a gallery or a form, to this value in the formula bar:
+If your connector provides tables, you add your data source, and then select the table in the data source that you want to manage. Power Apps both retrieve table data into your app and updates data in your data source automatically for you. For example, you can add a data source that contains a table named **Lessons** and then set the **Items** property of a control, such as a gallery or a form, to this value in the formula bar:
 
  ![Plain data source Items property.](./media/connections-list/ItemPropertyPlain.png)
 
@@ -55,7 +56,7 @@ If you need to handle custom data updates for action connectors, build a formula
 
 For more information about how to customize your formula for custom updates, see these articles:
 
-[Patch](functions/function-patch.md)<br>[Collect](functions/function-clear-collect-clearcollect.md)<br>[Update](functions/function-update-updateif.md)
+[Patch](functions/function-patch.md)<br />[Collect](functions/function-clear-collect-clearcollect.md)<br />[Update](functions/function-update-updateif.md)
 
 > [!NOTE]
 > To work with dynamic schema, you can use an **experimental** feature called **Dynamic schema**. Dynamic schema refers to the possibility that the same action may return a different table with different columns. Conditions that may cause the columns in the tables to differ include the action input parameters, the user or role that's executing the action, and the group in which the user is working, among others. For example, SQL Server stored procedures may return different columns if run with different inputs, or an Azure DevOps instance may use custom fields that aren't available by default. For working with dynamic schema, the [connector documentation](/connectors) shows **The outputs of this operation are dynamic.** as the return value.
@@ -106,7 +107,7 @@ This type of connection is also secure.  For example Twitter uses this type of a
 
 ### SQL User name and password authentication
 
-This type of connection isn't secure because it doesn't rely on end-user authentication. **It should only be used in cases where you can safely assume that everyone who has access to this connection can see and use all of the data to which the connection provides access.**  You can't reliably lock down portions of the data accessible within the connection. For instance, if the connection allows access to a single table, you can't rely on a userID to filter and only show data for that specific user within that table. For a reliable security, use more secure connection such as [Azure AD Integrated](connections-list.md#azure-active-directory-aad).  
+This type of connection isn't secure because it doesn't rely on end-user authentication. **It should only be used in cases where you can safely assume that everyone who has access to this connection can see and use all of the data to which the connection provides access.**  You can't reliably lock down portions of the data accessible within the connection. For instance, if the connection allows access to a single table, you can't rely on a userID to filter and only show data for that specific user within that table. For reliable security, use a more secure connection such as [Azure AD Integrated](connections-list.md#azure-active-directory-aad).  
 
 In SQL Server, this type of connection is called **SQL Server Authentication**.  Many other database data sources provide a similar capability.  When you publish your application, your users don't need to supply a unique user name and password.  They're using the user name and password you supply when you author the application.  The connection authentication to the data source is **Implicitly Shared** with your users.  Once the application is published, the connection is also published and available to your users.  Your end users can also create applications using any connection using SQL Server authentication that is shared with them.  Your users can't see the user name or password, but the connection will be available to them.  **There are valid scenarios for this type of connection. For instance if you have a read-only database that is available to everyone in the company. Reference data scenarios (for example, a corporate calendar) can be useful for this kind of connection.** More information: [Use Microsoft SQL Server securely with Power Apps](connections/sql-server-security.md)
 
@@ -120,12 +121,12 @@ Power Apps now has full preview support for **[Secure implicit connections](work
 > **Secure implicit connections** is now **On** by default for new apps.
 
 #### Notification to update your apps
-If you have applications that may be upgraded to use this feature then you will see a message on the Apps page. It will indicate the number of apps that need your attention.  
+If you have applications that may be upgraded to use this feature then you'll see a message on the Apps page. It indicates the number of apps that need your attention.  
 
    > [!div class="mx-imgBorder"]
    > ![Notification to update your apps.](./media/connections-list/attention-alert.png)
 
-Select the link and it will open a side panel that will list all of the apps that need attention.  
+Select the link and it opens a side panel that will list all of the apps that need attention.  
 
    > [!div class="mx-imgBorder"]
    > ![Side panel.](./media/connections-list/app-needs-attention.png)
@@ -162,8 +163,8 @@ When your app is republished and shared, then end-users won't have access to the
 #### Limitations
 
 1. All types of implicitly shared connections work such as action and tabular.
-2. Server and database names are hidden in network traces but visible in the consent dialog. Column names are not hidden.
-3. For tabular connectors, we only limit CRUD actions such as Get, Post, Put, or Delete. If you have permissions to **Put** then you have access to **Post**.
+2. Server and database names are hidden in network traces but visible in the consent dialog. Column names aren't hidden.
+3. For tabular connectors, we only limit CRUD actions such as Get, Post, Put, or Delete. If you have permissions to **Put**, then you have access to **Post**.
 4. Action based connectors limit based on the specific API being used in the application. 
 5. Warnings are still enabled in sharing. The warning around implicitly shared connections still warns while in private preview. However, your connection with this feature is secure – despite the warning.
 6. Publishing to an entire tenant, as opposed to specific groups or individuals isn't supported.  
@@ -174,21 +175,21 @@ This type of connection isn't secure because it doesn't rely on end-user authent
 
 ## Data sources in solutions
 
-Solutions are used for [application lifecycle management](/power-platform/alm/overview-alm) and provide additional capabilities for managing the lifecycle of **data sources**. If a canvas app is in a solution, [connection references](../data-platform/create-connection-reference.md) and [environment variables](../data-platform/environmentvariables.md) may be created to store information about the data sources. This ensures data sources can be changed or re-established when solutions are migrated to different environments. 
+Solutions are used for [application lifecycle management](/power-platform/alm/overview-alm) and provide other capabilities for managing the lifecycle of **data sources**. If a canvas app is in a solution, [connection references](../data-platform/create-connection-reference.md) and [environment variables](../data-platform/environmentvariables.md) may be created to store information about the data sources. This ensures data sources can be changed or re-established when solutions are migrated to different environments. 
 
 ## Rename data sources in apps
 
 To learn about renaming data sources in an app, and the difference between tabular and action-based data sources, go to [Rename Power Apps action-based data sources](rename-data-source.md).
 
 ## Connection consent dialog
 
-When users open an app that uses connectors for the first time, they'll see a "connection consent" dialog for the following purposes.
+When users open an app that uses connectors for the first time, they see a "connection consent" dialog for the following purposes.
 
 1. To inform users about the data sources accessed by the app.
 
 1. To outline the actions a connector may, or may not perform in an app. For example, for apps using the **Office 365 Users** connector, this could be the following.
 
-    - This app will be able to:
+    - This app is able to:
         - Read your full user profile
         - Read the full profile of all users
     - It won't be able to:
@@ -198,7 +199,7 @@ When users open an app that uses connectors for the first time, they'll see a "c
 
 1. To facilitate manual end-user authentication, when needed.
 
-For some connections, Power Platform can automatically authenticate a user to access a data source. However, if the automatic sign-in fails, this dialog prompts users to fix a connection by manually signing in. Power Platform can only attempt automatic sign-in for a connection when a data source pre-authorizes Microsoft’s Azure API connections service principal, granting it permission to perform single sign-on for a user when a connection is created. For more information on single sign-on, see [What is single sign-on (SSO)?](/azure/active-directory/manage-apps/what-is-single-sign-on)
+For some connections, Power Platform can automatically authenticate a user to access a data source. However, if the automatic sign-in fails, this dialog prompts users to fix a connection by manually signing in. Power Platform can only attempt automatic sign-in for a connection when a data source preauthorizes Microsoft’s Azure API connections service principal, granting it permission to perform single sign-on for a user when a connection is created. For more information on single sign-on, see [What is single sign-on (SSO)?](/azure/active-directory/manage-apps/what-is-single-sign-on)
 
 The following image is an example of the connection consent dialog for an app connecting to a SharePoint site.  
 
@@ -218,10 +219,10 @@ For select connectors, admins can suppress this dialog, and consent on behalf of
 Microsoft Power Platform is only able to suppress the consent dialog for connections to data sources where:
 
 1. There isn’t an obligation by the data source to show an explicit consent UI.
-1. The data source pre-authorizes Microsoft’s Azure API connections service principal to enable single-sign-on.
+1. The data source preauthorizes Microsoft’s Azure API connections service principal to enable single-sign-on.
 1. An admin configures an app to suppress the consent for the preceding connections.
 
-The pre-authorization of Microsoft’s Azure API connections service principal exists for Microsoft's first-party data sources, and may be configured by custom applications registered in an Azure AD tenant that are used by custom connectors. An admin manages consent suppression on a per-app basis (as opposed to connector basis), so suppression is managed at the most granular app experience level&mdash;this level of granularity prevents consent suppression for an organization’s "approved apps" from inadvertently suppressing consent for apps that aren't approved or reviewed.
+The preauthorization of Microsoft’s Azure API connections service principal exists for Microsoft's first-party data sources, and may be configured by custom applications registered in an Azure AD tenant that are used by custom connectors. An admin manages consent suppression on a per-app basis (as opposed to connector basis), so suppression is managed at the most granular app experience level&mdash;this level of granularity prevents consent suppression for an organization’s "approved apps" from inadvertently suppressing consent for apps that aren't approved or reviewed.
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]