Live publish

buck1ey · web-flow · commit 00f40621ee88 · 2023-02-23T11:00:01.000-08:00
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "powerapps-docs/maker/data-platform/data-platform-cr.md",
+      "redirect_url": "create-edit-entities-portal",
+      "redirect_document_id": false
+    },
     {
       "source_path": "powerapps-docs/cards/controls/repeat-for-every.md",
       "redirect_url": "/power-apps/cards/controls/control-reference#r",
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/control.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/control.md
@@ -3,8 +3,7 @@ title: Control Element | Microsoft Docs
 description: Defines the component's namespace, version and display information.
 ms.author: noazarur
 author: noazarur-microsoft
-manager: lwelicki
-ms.date: 11/21/2022
+ms.date: 02/22/2023
 ms.reviewer: jdaly
 ms.topic: reference
 ms.subservice: pcf
@@ -28,7 +27,7 @@ Model-driven and canvas apps
 |`constructor`|A method for initializing the object|[!INCLUDE [alphanumerictype-description](includes/alphanumerictype-description.md)]|Yes|Model-driven and canvas apps |
 |`control-type`|Whether the control is a standard control or a React control. The value of `virtual` indicates a React control using platform React library. Virtual controls are a feature in public preview. More information: [React controls & platform libraries (Preview) ](../react-controls-platform-libraries.md)|[!INCLUDE [controltype-description](includes/controltype-description.md)]|No|Model-driven and canvas apps |
 |`description-key`|Defines the description of the component that will be seen on the UI.|`string`|No|Model-driven and canvas apps |
-|`display-name-key`|Defines the name of the control that is displayed on the UI.|`string`|Yes|Model-driven and canvas apps  |  
+|`display-name-key`|Defines the name of the control that is displayed on the UI.|`string`|Yes|Model-driven and canvas apps  | 
 |`preview-image`|Image that will be used on the customization screens to show a preview of the component.|`string`|No|Model-driven apps|
 |`version`|Defines the version of the component defined in [Semantic Versioning](https://semver.org)|`string`|Yes|Model-driven and canvas apps |
 <!--|`hidden`|Defines whether the component should be hidden or not|[!INCLUDE [booleantype-description](includes/booleantype-description.md)]| No|Model-driven apps|-->
@@ -44,6 +43,7 @@ Model-driven and canvas apps
 |Element|Description|Occurrences|
 |--|--|--|
 |[data-set](data-set.md)|[!INCLUDE [data-set-description](includes/data-set-description.md)]|0 or more|
+|[external-service-usage](external-service-usage.md)|[!INCLUDE [external-service-usage-description](includes/external-service-usage-description.md)]|0 or 1|
 |[property](property.md)|[!INCLUDE [property-description](includes/property-description.md)]|0 or more|
 |[resources](resources.md)|[!INCLUDE [resources-description](includes/resources-description.md)]|1|
 |[type-group](type-group.md)|[!INCLUDE [type-group-description](includes/type-group-description.md)]|0 or more|
@@ -52,9 +52,13 @@ Model-driven and canvas apps
 ## Example
 
 ```xml
-<control namespace="MyNameSpace" constructor="JSHelloWorldControl" version="1.0.0"
- display-name-key="JS_HelloWorldControl_Display_Key" description-key="JS_HelloWorldControl_Desc_Key"
- control-type="standard" preview-image="img/preview.png">
+<control namespace="MyNameSpace"
+   constructor="JSHelloWorldControl"
+   version="1.0.0"
+   display-name-key="JS_HelloWorldControl_Display_Key"
+   description-key="JS_HelloWorldControl_Desc_Key"
+   control-type="standard"
+   preview-image="img/preview.png">
 </control>
   ```
 
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/___domain.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/___domain.md
@@ -0,0 +1,42 @@
+---
+title: ___domain element | Microsoft Docs
+description: Indicates the ___domain that the external-usage-element applies to.
+ms.author: noazarur
+author: noazarur-microsoft
+ms.date: 02/22/2023
+ms.reviewer: jdaly
+ms.topic: reference
+ms.subservice: pcf
+contributors:
+ - JimDaly
+---
+# ___domain Element
+
+[!INCLUDE [___domain-description](includes/___domain-description.md)]
+
+## Available for
+
+Canvas apps
+
+## Parent Elements
+
+|Element|Description|
+|--|--|
+|[external-service-usage](external-service-usage.md)|[!INCLUDE [external-service-usage-description](includes/external-service-usage-description.md)]|
+
+## Example
+
+```xml
+<external-service-usage enabled="true">
+   <domain>www.Microsoft.com</___domain>
+</external-service-usage>
+```
+
+### Related topics
+
+[Power Apps component framework manifest schema reference](index.md)<br/>
+[Power Apps component framework API reference](../reference/index.md)<br/>
+[Power Apps component framework overview](../overview.md)
+
+
+[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/external-service-usage.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/external-service-usage.md
@@ -0,0 +1,71 @@
+---
+title: external-service-usage element | Microsoft Docs
+description: Indicates whether this control is using external service or not.
+ms.author: noazarur
+author: noazarur-microsoft
+ms.date: 02/22/2023
+ms.reviewer: jdaly
+ms.topic: reference
+ms.subservice: pcf
+contributors:
+ - JimDaly
+---
+# external-service-usage element
+
+[!INCLUDE [external-service-usage-description](includes/external-service-usage-description.md)]
+
+## Available for
+
+Canvas apps
+
+## Parent Elements
+
+|Element|Description|
+|--|--|
+|[control](control.md)|[!INCLUDE [control-description](includes/control-description.md)]|
+
+## Child Elements
+
+
+|Element|Description|Occurrences|Available for|
+|--|--|--|-------|
+|[___domain](___domain.md)|[!INCLUDE [___domain-description](includes/___domain-description.md)]|0 or more|Canvas apps |
+
+
+## Example 1
+
+External usage enabled for www.microsoft.com only.
+
+```xml
+<external-service-usage enabled="true">
+   <domain>www.Microsoft.com</___domain>
+</external-service-usage>
+```
+
+## Example 2
+
+External usage enabled for multiple domains.
+
+```xml
+<external-service-usage enabled="false">
+  <domain>www.contoso.com</___domain>
+  <domain>www.yourcompany.com</___domain>
+</external-service-usage>
+```
+
+## Example 3
+
+External usage is not enabled.
+
+```xml
+<external-service-usage enabled="false" />
+```
+
+### Related topics
+
+[Power Apps component framework manifest schema reference](index.md)<br/>
+[Power Apps component framework API reference](../reference/index.md)<br/>
+[Power Apps component framework overview](../overview.md)
+
+
+[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/___domain-description.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/___domain-description.md
@@ -0,0 +1 @@
+Specifies the ___domain within the [external-service-usage element](../external-service-usage.md)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/external-service-usage-description.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/includes/external-service-usage-description.md
@@ -0,0 +1 @@
+Indicates whether this control is using external service or not. If it is, set the enabled attribute flag as true and add the external service ___domain to the `<domain>` property. A control that uses any external service is a premium control and the end user will need a Power Apps license to open an app with a premium control. More information: [Licensing](../../overview.md#licensing)
diff --git a/powerapps-docs/developer/component-framework/manifest-schema-reference/index.md b/powerapps-docs/developer/component-framework/manifest-schema-reference/index.md
@@ -3,8 +3,7 @@ title: Power Apps component framework manifest schema reference | Microsoft Docs
 description: This section contains reference documentation for manifest schema generated using Microsoft Power Platform CLI.
 ms.author: noazarur
 author: noazarur-microsoft
-manager: lwelicki
-ms.date: 05/27/2022
+ms.date: 02/22/2023
 ms.reviewer: jdaly
 ms.topic: reference
 ms.subservice: pcf
@@ -17,14 +16,16 @@ contributors:
 This section contains reference documentation for manifest schema generated using Microsoft Power Platform CLI.
 
 > [!IMPORTANT]
-> The **Available for** tab shows which elements are supported by model-driven and canvas apps. It is recommended to check the **Available for** section for each individual property whether it is supported or not. For example, the **code** element is supported for both model-driven and canvas apps, but **html** and **img** properties in **code** elements doesn't support canvas apps. 
+> The **Available for** tab shows which elements are supported by model-driven and canvas apps. It is recommended to check the **Available for** section for each individual property whether it is supported or not. For example, the **code** element is supported for both model-driven and canvas apps, but **html** and **img** properties in **code** elements doesn't support canvas apps.
 
 |Element|Description|Available for|
 |----|-----------|-----|
 |[code](code.md)|[!INCLUDE [code-description](includes/code-description.md)]|Model-driven and canvas apps|
 |[control](control.md)|[!INCLUDE [control-description](includes/control-description.md)]|Model-driven and canvas apps|
 |[css](css.md)|[!INCLUDE [css-description](includes/css-description.md)]|Model-driven and canvas apps|
 |[data-set](data-set.md)|[!INCLUDE [data-set-description](includes/data-set-description.md)]|Model-driven apps|
+|[___domain](___domain.md)|[!INCLUDE [___domain-description](includes/___domain-description.md)]|Canvas apps|
+|[external-service-usage](external-service-usage.md)|[!INCLUDE [external-service-usage-description](includes/external-service-usage-description.md)]|Canvas apps|
 |[feature-usage](feature-usage.md)|The feature-usage element acts as a wrapper around the `uses-feature` elements, which themselves allow developers to declare which features their component wants to use. If there are no uses-feature elements defined, the feature-usage element is not required.|Model-driven apps|
 |[img](img.md)|[!INCLUDE [img-description](includes/img-description.md)]|Model-driven apps|
 |[manifest](manifest.md)|Manifest is the metadata file that defines a component. It is an XML document that describes<br/> - The namespace of the component.<br/> - The kind of data it can be configured, either a field or a data-set.<br/> - Any properties that can be configured in the application when the component is added.<br/> - A list of resource files that the component needs.<br/> - One of them must be a JavaScript web resource. This JavaScript must include a function that will instantiate an object. This implements an interface that exposes methods that are required for the component to work. This is called the component implementation library.<br/> - The name of a JavaScript function in the component implementation library that will return an object that applies the required interface.<br/> When someone configures a component in the application, the data in the manifest filters out the available components so that only valid components for the context are available for configuration. The properties defined in the manifest for a component are rendered as configuration fields so that the person configuring the control can specify values. These property values are then available to your component function at run time.|Model-driven and canvas apps|
diff --git a/powerapps-docs/developer/component-framework/toc.yml b/powerapps-docs/developer/component-framework/toc.yml
@@ -442,6 +442,10 @@ items:
         href: manifest-schema-reference/css.md
       - name: data-set
         href: manifest-schema-reference/data-set.md
+      - name: ___domain
+        href: manifest-schema-reference/___domain.md
+      - name: external-service-usage
+        href: manifest-schema-reference/external-service-usage.md
       - name: feature-usage
         href: manifest-schema-reference/feature-usage.md
       - name: img
diff --git a/powerapps-docs/maker/TOC.yml b/powerapps-docs/maker/TOC.yml
@@ -2498,6 +2498,8 @@
         href: ./data-platform/export-solutions.md
       - name: Import solutions
         href: ./data-platform/import-update-export-solutions.md
+      - name: Use pipelines to simplify solution deployment
+        href: ./data-platform/use-pipelines.md
       - name: Update or upgrade solutions
         href: ./data-platform/update-solutions.md
       - name: Other solution tasks
diff --git a/powerapps-docs/maker/data-platform/azure-synapse-link-synapse.md b/powerapps-docs/maker/data-platform/azure-synapse-link-synapse.md
@@ -2,7 +2,7 @@
 title: "Create an Azure Synapse Link for Dataverse with your Azure Synapse Workspace | MicrosoftDocs"
 description: "Learn how to export table data to Azure Synapse Analytics in Power Apps"
 ms.custom: ""
-ms.date: 01/05/2023
+ms.date: 02/23/2023
 ms.reviewer: "Mattp123"
 ms.suite: ""
 ms.tgt_pltfrm: ""
@@ -39,19 +39,20 @@ You can use the Azure Synapse Link to connect your Microsoft Dataverse data to A
 
 ## Prerequisites
 
-- Azure Data Lake Storage Gen2: You must have an Azure Data Lake Storage Gen2 account and **Owner** and **Storage Blob Data Contributor** role access. Your storage account must enable **Hierarchical namespace** and **public network access** for both initial setup and delta sync. **Allow storage account key access** is required only for the initial setup. We recommend that replication is set to **read-access geo-redundant storage (RA-GRS)**.  
+- Dataverse: You must have the Dataverse **system administrator** security role. Additionally, tables you want to export via Synapse Link must have the **Track changes** property enabled. More information: [Advanced options](create-edit-entities-portal.md#advanced-options)
 
-- Synapse workspace: You must have a Synapse workspace and the **Synapse Administrator** role access within the Synapse Studio. The Synapse workspace must be in the same region as your Azure Data Lake Storage Gen2 account with **public network access** enabled. The storage account must be added as a linked service within the Synapse Studio. To create a Synapse workspace, go to [Creating a Synapse workspace](/azure/synapse-analytics/get-started-create-workspace).
+- Azure Data Lake Storage Gen2: You must have an Azure Data Lake Storage Gen2 account and **Owner** and **Storage Blob Data Contributor** role access. Your storage account must enable **Hierarchical namespace** and **public network access** for both initial setup and delta sync. **Allow storage account key access** is required only for the initial setup.  
+
+- Synapse workspace: You must have a Synapse workspace and the **Synapse Administrator** role access within the Synapse Studio. The Synapse workspace must be in the same region as your Azure Data Lake Storage Gen2 account with **allowAll** IP addresses access rule. The storage account must be added as a linked service within the Synapse Studio. To create a Synapse workspace, go to [Creating a Synapse workspace](/azure/synapse-analytics/get-started-create-workspace).
 
 > [!NOTE]
 >
 > - The storage account and Synapse workspace must be created in the same Azure Active Directory (Azure AD) tenant as your Power Apps tenant.
 > - The storage account and Synapse workspace must be created in the same region as the Power Apps environment you will use the feature in and the same resource group.
 > - Using private endpoints for storage account or Synapse workspace isn't supported.
 > - You must have **Reader** role access to the resource group with the storage account and Synapse workspace.  
-> - To link the environment to Azure Data Lake Storage Gen2, you must have the Dataverse system administrator security role.
-> - Only tables that have change tracking enabled can be exported.
 > - When you add multiple users to the synapse workspace, they must have the **Synapse Administrator** role access within the Synapse Studio and the **Storage Blob Data Contributor** role on the Azure Data Lake Storage Gen2 account.
+> - The creation of Synapse Link profiles under a single DV environment is limited to a maximum of 10.
 
 ## Connect Dataverse to Synapse workspace
 
diff --git a/powerapps-docs/maker/data-platform/create-edit-entities-portal.md b/powerapps-docs/maker/data-platform/create-edit-entities-portal.md
@@ -63,6 +63,8 @@ Select **Enable Attachments** to append notes and files to records for this tabl
 
 Select the **Primary column** tab if you want to change the **Display Name** or **Name** of the primary column. The primary column is used by lookup fields when establishing relationships with other tables.
 
+### Advanced options
+
 Select **Advanced options** to display additional properties that are optional for a table.
 
 |Property |Description|
@@ -73,7 +75,7 @@ Select **Advanced options** to display additional properties that are optional f
 | **Choose a table image**  | You can choose whether to display an image for the table. This image is displayed in Power Apps in some design areas. Notice that the image doesn't appear in apps using the table. To display images in apps, use the image column. More information: [Image columns](types-of-fields.md#image-columns) |
 | **Color** | Set a color to be used for the table in model-driven apps.  |
 |**Apply duplicate detection rules**   | If duplicate detection is enabled for your organization, enabling this allows you to create duplicate detection rules for this table.  |
-|**Track changes**   | Enables data synchronization in a performant way by detecting what data has changed since the data was initially extracted or last synchronized.  |
+|**Track changes**   | Enables data synchronization in a performant way by detecting what data has changed since the data was initially extracted or last synchronized.  This option must be enabled for certain features such as Azure Synapse Link for Dataverse. |
 | **Provide custom help**  | When selected, set a **Help URL** to control what page users will see when they select the help button in the application. Use this to provide guidance specific to your company processes for the table.  |
 | **Audit changes to its data**  | When auditing is enabled for your organization, this allows for changes to table records to be captured over time. When you enable auditing for a table, auditing is also enabled on all its fields. You can select or clear fields that you want to enable auditing on.  |
 | **Leverage quick create form if available**  |After you've created and published a Quick Create Form for this table, people will have the option to create a new record using the Create button in the navigation pane. More information: [Create and design model-driven app forms](../model-driven-apps/create-design-forms.md)  <br /> When this is enabled for a custom activity table, the custom activity will be visible in the group of activity entities when people use the **Create** button in the navigation pane. However, because activities don’t support quick create forms, the main form will be used when the custom table icon is selected.  |
diff --git a/powerapps-docs/maker/data-platform/use-pipelines.md b/powerapps-docs/maker/data-platform/use-pipelines.md
@@ -0,0 +1,20 @@
+---
+title: Use pipelines in Power Platform to deploy solutions
+description: Pipelines in Power Platform are the easiest way to deploy solutions. 
+author: Mattp123
+ms.author: matp
+ms.topic: overview
+ms.date: 02/23/2023
+ms.custom: template-overview
+ms.service: powerapps
+ms.subservice: dataverse-maker
+contributors:
+- caburk
+---
+# Use pipelines in Power Platform to deploy solutions
+
+Easily deploy solutions to test and production environments using pipelines in Power Platform. Once pipelines are in place, makers can initiate in-product deployments with a few clicks. Makers do so directly within their development environments. More information: [Overview of pipelines in Power Platform](/power-platform/alm/pipelines)
+
+## See also
+
+[Solutions overview](solutions-overview.md)
diff --git a/powerapps-docs/maker/model-driven-apps/rich-text-editor-control.md b/powerapps-docs/maker/model-driven-apps/rich-text-editor-control.md
@@ -469,8 +469,7 @@ Default:
 </td>
 
 <td>
-
-  By default, images will be uploaded using the client API. As soon as an image is added to the editor, it will be uploaded to the platform. To process images, set this property to true.
+  By default, images will be uploaded using the client API. As soon as an image is added to the editor, it will be uploaded to the platform. To store images as base64 strings directly in the column configured to use the rich text editor control set this value to **true**.
 </td>
 <td>
 
diff --git a/powerapps-docs/maker/portals/admin/portal-admin-roles.md b/powerapps-docs/maker/portals/admin/portal-admin-roles.md
@@ -119,7 +119,7 @@ To assign a user the System administrator Power Platform role, go to [Configure
 
 *System customizer* is a Microsoft Power Platform security role. This role has full permissions to customize a Microsoft Power Platform environment.
 
-To assign a user the System administrator Power Platform role, go to [Configure user security to resources in an environment](/power-platform/admin/database-security).
+To assign a user the System Customizer Power Platform role, go to [Configure user security to resources in an environment](/power-platform/admin/database-security).
 
 ### Power Platform administrator
 

Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,10 @@`
`1`	`1`	`{`
`2`	`2`	`"redirections": [`
	`3`	`+ {`
	`4`	`+ "source_path": "powerapps-docs/maker/data-platform/data-platform-cr.md",`
	`5`	`+ "redirect_url": "create-edit-entities-portal",`
	`6`	`+ "redirect_document_id": false`
	`7`	`+ },`
`3`	`8`	`{`
`4`	`9`	`"source_path": "powerapps-docs/cards/controls/repeat-for-every.md",`
`5`	`10`	`"redirect_url": "/power-apps/cards/controls/control-reference#r",`
Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	`+Specifies the ___domain within the [external-service-usage element](../external-service-usage.md)`
Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	+Indicates whether this control is using external service or not. If it is, set the enabled attribute flag as true and add the external service ___domain to the `<___domain>` property. A control that uses any external service is a premium control and the end user will need a Power Apps license to open an app with a premium control. More information: [Licensing](../../overview.md#licensing)