Live publish

Author: buck1ey

powerapps-docs/developer/data-platform/download-tools-nuget.md

@@ -57,7 +57,7 @@ You can download all SDK tools using the PowerShell script provided below. Note
     ##
     ./nuget install Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool -O .\Tools
     md .\Tools\PluginRegistration
-    $prtFolder = Get-ChildItem ./Tools | Where-Object {$_.Name -match 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool.'}
+    $prtFolder = (Get-ChildItem ./Tools | Where-Object {$_.Name -match 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool.'}).Name
     move .\Tools\$prtFolder\tools\*.* .\Tools\PluginRegistration
     Remove-Item .\Tools\$prtFolder -Force -Recurse
     

powerapps-docs/developer/data-platform/xrm-tooling/use-connection-strings-xrm-tooling-connect.md

@@ -2,7 +2,7 @@
 title: "Use connection strings in XRM tooling to connect to Microsoft Dataverse (Dataverse)| Microsoft Docs"
 description: "XRM tooling enables you to connect to your Microsoft Dataverse environment by using connection strings"
 ms.custom: ""
-ms.date: 11/13/2019
+ms.date: 1/6/2022
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -60,7 +60,7 @@ CrmServiceClient svc = new CrmServiceClient(ConnectionString);
 |`UserName`, `User Name`, `UserId`, or `User Id`|Specifies the user's identification name associated with the credentials.|  
 |`Password`|Specifies the password for the user name associated with the credentials.|  
 |`HomeRealmUri` or `Home Realm Uri`|Specifies the Home Realm Uri.|  
-|`AuthenticationType` or `AuthType`|Specifies the authentication type to connect to Dataverse environment. Valid values are: `AD`, `IFD` (AD FS enabled), `OAuth`, `Certificate`, `ClientSecret`, or `Office365`. However,  only `OAuth`, `Certificate`, `ClientSecret` and `Office365` are permitted values for Dataverse environments.|  
+|`AuthenticationType` or `AuthType`|Specifies the authentication type to connect to Dataverse environment. Valid values are: `AD`, `IFD` (AD FS enabled), `OAuth`, `Certificate`, `ClientSecret`, or `Office365`. However,  only `OAuth`, `Certificate`, `ClientSecret` and `Office365` are permitted values for Dataverse environments.<br/><br/>**NOTE**: `Office365` authentication type is deprecated, and we recommend to use `OAuth` as the preferred authentication type. More information: [What should I do to fix my application code if affected?](/powerapps/developer/data-platform/authenticate-office365-deprecation#what-should-i-do-to-fix-my-application-code-if-affected)|  
 |`RequireNewInstance`|Specifies whether to reuse an existing connection if recalled while the connection is still active. If set to `true`, will force the system to create a unique connection. If set to `false` the existing connection can be reused.|  
 |`ClientId`, `AppId` or `ApplicationId`|Specifies the `ClientID` assigned when you registered your application in Azure Active Directory or Active Directory Federation Services (AD FS).|
 |`ClientSecret` or `Secret` |Required when Auth Type is set to `ClientSecret`. Client Secret string to use for authentication.|
@@ -86,7 +86,10 @@ The following examples show how you can use connection strings for connecting to
 
 ### Named account using Office365  
 
-Create a new connection to Dataverse using a UserName or Password via Office365. This `AuthType` is deprecated and we recommend to use `OAuth` as the preferred authentication type. More information: [Authenticate using Office365](/power-platform/important-changes-coming#deprecation-of-office365-authentication-type-and-organizationserviceproxy-class-for-connecting-to-dataverse)
+Create a new connection to Dataverse using a UserName or Password via Office365. 
+
+> [!NOTE]
+> This `AuthType` is deprecated and we recommend to use `OAuth` as the preferred authentication type. More information: [Authenticate using Office365](/power-platform/important-changes-coming#deprecation-of-office365-authentication-type-and-organizationserviceproxy-class-for-connecting-to-dataverse)
 
 ```xml
 <add name="MyCDSServer" 

powerapps-docs/docfx.json

@@ -45,7 +45,8 @@
         "AshleyWoodruff"
       ],
       "breadcrumb_path": "breadcrumb/toc.yml",
-      "extendBreadcrumb": true,      
+      "extendBreadcrumb": true,
+      "ms.suite": "office",
       "titleSuffix": "Power Apps",
       "feedback_system": "GitHub",
       "feedback_github_repo": "MicrosoftDocs/powerapps-docs",

powerapps-docs/maker/portals/configure/add-fixed-layouts.md

@@ -1,6 +1,6 @@
 ---
 title: Add fixed page layouts
-description: Instructions to add fixed layouts to be available within the portals Studio.
+description: Instructions to add fixed layouts to be available within portals Studio.
 author: ankitavish
 ms.service: powerapps
 ms.topic: conceptual
@@ -15,46 +15,41 @@ contributors:
 ---
 
 # Add fixed page layouts
+When you add a new webpage to a portal by using [Power Apps portals Studio](../portal-designer-anatomy.md), you can choose either **Layouts** or **Fixed layouts**. If there are no fixed layouts available in portals Studio but you'd like to use the layout of an existing web template, you can add these templates as fixed page layouts by creating page template records with the [Portal Management app](configure-portal.md).
 
-When you add a new web page to a portal using the [portals Studio](../portal-designer-anatomy.md), you can choose either **Layouts** or **Fixed Layouts**. If there are no existing fixed layouts available in the portals Studio, you can add existing web templates as fixed page layouts by creating page template records using the [Portal Management app](configure-portal.md).
+:::image type="content" source="media/add-fixed-layouts/no-fixed-layouts.png" alt-text="Screenshot showing the message 'There are no fixed layouts.'":::
 
-:::image type="content" source="media/add-fixed-layouts/no-fixed-layouts.png" alt-text="No fixed layouts.":::
-
-## Add fixed layouts using page templates
-
-A new portal is provisioned with many fixed layout web templates. Both the provided and [custom web templates](../liquid/create-custom-template.md) can be added to the portals Studio by creating corresponding [page template](page-templates.md) records.
+A new portal is provisioned with several fixed layout web templates. You can add these templates (whether provided by default or in a [custom web template](../liquid/create-custom-template.md)) to portals Studio by creating corresponding [page template](page-templates.md) records.
 
 1. In the Portal Management app, select **Page Templates**.
 
-1. Select **New**.
-
-    The following web templates are provided as part of the default portal template:
+1. Select **New**, and then select a web template. The following web templates are provided as part of the default portal.
 
-    | Web Template | Suggested Page Template Name |
+    | Web template | Suggested page template name |
     | - | - |
-    | Full Page | Page with child links |
-    | Full Page without Child Links | Page with title |
+    | Full Page | **Page with child links** |
+    | Full Page without Child Links | **Page with title** |
 
-1. Add a new Page Template record with the following details;
+1. Add a new page template record with the following details.
 
-    | Page Template setting | Value |
+    | Page template setting | Value |
     | - | - |
-    | Name | *add a name, or choose suggested value, for example; Page with title* |
-    | Website | *choose the corresponding website.* |
-    | Type | Web Template |
-    | Web Template | *choose corresponding provided or custom web template, for example; Full Page without Child Links* |
-    | Use Website Header and Footer | checked |
-    | Is Default | Not checked |
-    | Table Name | adx_webpage |
+    | Name | Add a name, or choose a suggested value (for example, **Page with title**). |
+    | Website | Choose the corresponding website. |
+    | Type | **Web Template** |
+    | Web Template | Choose the corresponding provided template (for example, **Full Page without Child Links**) or another web template. |
+    | Use Website Header and Footer | Selected |
+    | Is Default | Not selected |
+    | Table Name | **adx_webpage** |
     | Description | Optional |
 
-    :::image type="content" source="media/add-fixed-layouts/page-with-title.png" alt-text="No fixed layouts available.":::
+    :::image type="content" source="media/add-fixed-layouts/page-with-title.png" alt-text="Page Template record showing the aforementioned settings.":::
 
-1. In the portals Studio, select **Sync configuration**.
+1. In portals Studio, select **Sync configuration**.
 
-1. The fixed layouts should now be available when creating web pages using the portals Studio.
+   The fixed layouts will now be available when you create webpages in portals Studio.
 
-    :::image type="content" source="media/add-fixed-layouts/fixed-layouts.png" alt-text="Add pages using fixed layouts.":::
+   :::image type="content" source="media/add-fixed-layouts/fixed-layouts.png" alt-text="Screenshot showing a list of fixed layouts to choose from.":::
 
 ### See also
 

powerapps-docs/maker/portals/contact-us-sample.md

@@ -1,6 +1,6 @@
 ---
 title: Contact us sample
-description: Overview of the Contact us sample page that is part of the portal starter template.
+description: Overview of the Contact us sample page that's part of the portal starter template.
 author: ankitavish
 ms.service: powerapps
 ms.topic: conceptual
@@ -16,65 +16,58 @@ contributors:
 
 # Contact us sample
 
-When you create a new portal using the *portal from blank* template, it will create an example web page called *Contact us*. This web page provides a working example of how portal users can enter information into a form that will be stored in a Dataverse table.
+When you create a new portal by using the **Portal from blank** template, it creates an example page called **Contact us**. This page provides a working example of how portal users can enter information into a form that will be stored in a Dataverse table.
 
 :::image type="content" source="media/contact-us-sample/contact-us-page.png" alt-text="Contact Us page.":::
 
-## Contact us web page
+## Contact us webpage
 
-The contact us web page can be viewed in the [portals Studio](portal-designer-anatomy.md) by selecting **Pages and navigation** from the toolbelt and choosing **Contact us**. 
+The contact us webpage can be viewed in Power Apps [portals Studio](portal-designer-anatomy.md) by selecting **Pages and navigation** from the toolbar and then selecting **Contact us**. This webpage is composed of three sections:
 
-The example web page is composed of three sections;
+- A [text component](add-text.md) for the page title, set to "Contact us".
 
-- A section with a [text component](add-text.md) for the page title, set to "Contact us".
+- A [basic form component](add-form.md) named **Simple contact us form**, which is linked to the Dataverse table Feedback and set to Insert mode.
 
-- A section with a [basic form component](add-form.md) named *simple contact us form* linked to the Dataverse table *feedback* set to *Insert* mode.
-
-- A section with an [IFrame component](add-iframe.md) linked to Bing maps.
+- An [iframe component](add-iframe.md) linked to Bing maps.
 
 > [!NOTE]
-> The Bing maps link does not have any functionality or geo-___location enabled. It is provided as an example IFrame component.
+> The Bing maps link doesn't have any functionality or geo-___location enabled. It's provided as an example iframe component.
 
-:::image type="content" source="media/contact-us-sample/contact-us-portalstudio.png" alt-text="Contact us page in the portal Studio.":::
+:::image type="content" source="media/contact-us-sample/contact-us-portalstudio.png" alt-text="Contact us page in portals Studio.":::
 
 ## Table permissions
 
-To allow portal users to be able to insert records to the feedback table, [table permissions](/configure/assign-entity-permissions.md) are configured to provide *create*, *read*, *write*, and *delete* permissions for the *Administrators*, *Anonymous Users*, and *Authenticated Users* [webroles](/configure/create-web-roles.md).
+To allow portal users to be able to insert records into the feedback table, [table permissions](/configure/assign-entity-permissions.md) are configured to provide Create, Read, Write, and Delete permissions for the Administrator, Anonymous User, and Authenticated User [web roles](/configure/create-web-roles.md).
 
 :::image type="content" source="media/contact-us-sample/feedback-tablepermissions.png" alt-text="Feedback table permissions.":::
 
 > [!NOTE]
-> It is good practice to review your security requirements before providing access to Dataverse tables using portals.
+> It's good practice to review your security requirements before providing access to Dataverse tables through portals.
 
 ## Basic form metadata
 
-To make all the form fields required, [basic form metadata](/configure/configure-basic-form-metadata.md) records were added to the basic form using the [Portal Management app](/configure/configure-portal.md).
+All the form fields that the **Contact us** form requires have been created using [basic form metadata](/configure/configure-basic-form-metadata.md). These settings can be viewed and modified using the [Portal Management app](/configure/configure-portal.md).
 
 :::image type="content" source="media/contact-us-sample/basicform-metadata.png" alt-text="Basic form metadata.":::
 
-## View Feedback Data
-
-To view the feedback data collected using the sample web page, go to the [Power Apps maker portal](https://make.powerapps.com). 
+## View feedback data
 
-1. Select the **Dataverse** tab.
+To view the feedback data that was collected by the sample webpage, go to the [Power Apps maker portal](https://make.powerapps.com). 
 
-1. Select **Tables**.
+1. On the left pane, expand **Dataverse**, and then select **Tables**.
 
-1. Select **Feedback**.
-
-1. Select **Data**.
+1. Select **Feedback**, and then select **Data**.
 
 :::image type="content" source="media/contact-us-sample/feedback-dataverse.png" alt-text="Feedback viewed in Dataverse.":::
 
-You can also create a [Power App (canvas or model-driven)](../index.md) or another portal page to view the feedback data.
+You can also create an app in Power Apps [(canvas or model-driven)](../index.md) or another portal page to view the feedback data.
 
 ### See also
 
-- [Dataverse Form Designer](../model-driven-apps/form-designer-overview.md)
-- [Add form](add-form.md)
-- [Power Apps portals Studio](portal-designer-anatomy.md)
-- [Create and manage webpages](create-manage-webpages.md)
-- [WYSIWYG editor](compose-page.md)
-
+[Dataverse Form Designer](../model-driven-apps/form-designer-overview.md)  
+[Add form](add-form.md)  
+[Power Apps portals Studio](portal-designer-anatomy.md)  
+[Create and manage webpages](create-manage-webpages.md)  
+[WYSIWYG editor](compose-page.md)
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]