Merge branch 'master' into tapanm_cds_connector_update

Author: tapanm-MSFT

.openpublishing.redirection.json

@@ -1,5 +1,15 @@
 {
   "redirections": [
+    {
+      "source_path": "powerapps-docs/developer/common-data-service/fill-app-submission-form-appsource.md",
+      "redirect_url": "register-microsoft-partner-network",
+      "redirect_document_id": "false"
+    },    
+    {
+      "source_path": "powerapps-docs/maker/portals/configure/view-email-in-timeline.md",
+      "redirect_url": "view-all-activities-in-portal-timeline",
+      "redirect_document_id": "false"
+    }, 
     {
       "source_path": "powerapps-docs/maker/canvas-apps/working-with-environments.md",
       "redirect_url": "/power-platform/admin/working-with-environments",

powerapps-docs/developer/common-data-service/TOC.yml

@@ -361,15 +361,13 @@
   - name: Publish your app on AppSource
     href: publish-app-appsource.md
     items:
-    - name: 'Step 1: Fill the app submission form on AppSource'
-      href: fill-app-submission-form-appsource.md
-    - name: 'Step 2: Register for Microsoft Partner Network account'
+    - name: 'Step 1: Create a Microsoft Partner Center account'
       href: register-microsoft-partner-network.md
-    - name: 'Step 3: Create a managed solution for your app'
+    - name: 'Step 2: Create a managed solution for your app'
       href: create-solution-app-appsource.md
-    - name: 'Step 4: Create an AppSource package for your app'
+    - name: 'Step 3: Create an AppSource package for your app'
       href: create-package-app-appsource.md
-    - name: 'Step 5: Store your AppSource Package on Azure Storage and generate a URL with SAS key'
+    - name: 'Step 4: Store your AppSource Package on Azure Storage and generate a URL with SAS key'
       href: store-appsource-package-azure-storage.md
     - name: 'Next steps: Submit your app on Partner Center'
       href: next-steps-submit-app-cloud-partner-portal.md

powerapps-docs/developer/common-data-service/appendix-app-design-best-practices-checklist.md

@@ -1,6 +1,6 @@
 ---
 title: "Appendix: App design best practices checklist (PowerApps) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
-description: "Use the app design checklist to evaluate your app design in PowerApps." # 115-145 characters including spaces. This abstract displays in the search result.
+description: "Use the app design checklist to evaluate your app design in Power Apps." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
 ms.date: 03/20/2019
 ms.reviewer: "kvivek"

powerapps-docs/developer/common-data-service/best-practices/TOC.yml

@@ -28,6 +28,8 @@
         href: business-logic/set-timeout-for-external-calls-from-plug-ins.md
       - name: Use InvalidPluginExecutionException in plug-ins and workflow activities
         href: business-logic/use-invalidpluginexecutionexception-plugin-workflow-activities.md
+      - name: Verify certification dependencies for plug-ins making outbound calls
+        href: business-logic/verify-certification-dependencies.md
   - name: Work with data using code
     href: work-with-data/index.md
     items:

powerapps-docs/developer/common-data-service/best-practices/business-logic/avoid-batch-requests-plugin.md

@@ -13,7 +13,7 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 11/27/2019
+ms.date: 12/06/2019
 ms.author: jowells
 search.audienceType: 
   - developer
@@ -31,7 +31,7 @@ search.app:
 
 ## Symptoms
 
-Due to their long-running nature, using <xref:Microsoft.Xrm.Sdk.Messages.ExecuteMultipleRequest> or <xref:Microsoft.Xrm.Sdk.Messages.ExecuteTransactionRequest> message request classes within the context of a plug-in or workflow activity expose sandbox-isolated plug-in types to the two-minute (2000-ms) channel timeout exception and can degrade the user experience for synchronous registrations.
+Due to their long-running nature, using <xref:Microsoft.Xrm.Sdk.Messages.ExecuteMultipleRequest> or <xref:Microsoft.Xrm.Sdk.Messages.ExecuteTransactionRequest> message request classes within the context of a plug-in or workflow activity expose sandbox-isolated plug-in types to the two-minute (12000ms) channel timeout exception and can degrade the user experience for synchronous registrations.
 
 
 <a name='guidance'></a>

powerapps-docs/developer/common-data-service/best-practices/business-logic/index.md

@@ -1,6 +1,6 @@
 ---
 title: "Developers: Best practices and guidance regarding plug-in and workflow development for the Common Data Service | Microsoft Docs"
-description: Best practices and guidance regarding plug-in and workflow development for developers of the Common Data Service in PowerApps.
+description: Best practices and guidance regarding plug-in and workflow development for developers of the Common Data Service in Power Apps.
 services: ''
 suite: powerapps
 documentationcenter: na
@@ -27,7 +27,7 @@ This list below contains all of the guidance and best practices regarding the pl
 
 |Best Practice  |Description  |
 |---------|---------|
-|[Avoid usage of batch request types in plug-ins and workflow activities](avoid-batch-requests-plugin.md)     |You shouldn't use ExecuteMultipleRequest or ExecuteTransactionRequest message request classes within the context of a plug-in or workflow activity.         |
+|[Avoid usage of batch request types in plug-ins and workflow activities](avoid-batch-requests-plugin.md)|You shouldn't use ExecuteMultipleRequest or ExecuteTransactionRequest message request classes within the context of a plug-in or workflow activity.|
 |[Develop IPlugin implementations as stateless](develop-iplugin-implementations-stateless.md)     |Members of classes that implement IPlugin are exposed to potential thread-safety issues which could lead to data inconsistency or performance problems.         |
 |[Do not duplicate plug-in step registration](do-not-duplicate-plugin-step-registration.md)     |Duplicate plug-in step registration will cause the plug-in to fire multiple times on the same message/event.         |
 |[Do not use parallel execution within plug-ins and workflow activities](do-not-use-parallel-execution-in-plug-ins.md)|Multi or parallel threading within plug-ins or custom workflow activities is not supported.|
@@ -39,6 +39,7 @@ This list below contains all of the guidance and best practices regarding the pl
 |[Set KeepAlive to false when interacting with external hosts in a plug-in](set-keepalive-false-interacting-external-hosts-plugin.md)     |KeepAlive property set to true in the HTTP request header or not explicitly defined as false can cause increased execution times of plug-ins.         |
 |[Set Timeout when making external calls in a plug-in](set-timeout-for-external-calls-from-plug-ins.md)     |Limit the time period that external calls will expect a response within plug-ins.|   
 |[Use InvalidPluginExecutionException in plug-ins and workflow activities](use-invalidpluginexecutionexception-plugin-workflow-activities.md)     |Use InvalidPluginExecutionException when raising errors within the context of a plug-in or workflow activity.         |
+|[Verify certification dependencies for plug-ins making outbound calls](verify-certification-dependencies.md)|Ensure that any certificates that your code depends on for outbound calls has a valid chain of certificates.|
 
 ### See Also
 

powerapps-docs/developer/common-data-service/best-practices/business-logic/verify-certification-dependencies.md

@@ -0,0 +1,63 @@
+---
+title: "Verify certification dependencies for plug-ins making outbound calls | MicrosoftDocs"
+description: "Ensure that any certificates that your code depends on for outbound calls has a valid chain of certificates."
+services: ''
+suite: powerapps
+documentationcenter: na
+author: JimDaly
+manager: ryjones
+editor: ''
+tags: ''
+ms.service: powerapps
+ms.devlang: na
+ms.topic: article
+ms.tgt_pltfrm: na
+ms.workload: na
+ms.date: 01/08/2020
+ms.author: jdaly
+search.audienceType: 
+  - developer
+search.app: 
+  - PowerApps
+  - D365CE
+---
+# Verify certification dependencies for plug-ins making outbound calls
+
+**Category**: Maintainability, Supportability
+
+**Impact potential**: High
+
+<a name='symptoms'></a>
+
+## Symptoms
+
+You may get this error when your plug-in makes an https call to an external resource:
+
+`WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.`
+
+
+<a name='guidance'></a>
+
+## Guidance
+
+You should verify that the site you want to connect with has a valid chain of certificates. Use one of the online test tools such as [Qualys SSL Labs SSL Server Test](https://www.ssllabs.com/ssltest/analyze.html) to verify that the site provides a valid chain of certificates.
+
+
+<a name='additional'></a>
+
+## Additional information
+
+You may encounter this when connecting to a new endpoint for the first time or when something about the certificate has changed.
+
+When the code in your plug-in running in the sandbox attempts to connect to an external endpoint using https, the CDS Sandbox will start SSL/TLS negotiation. The endpoint presents a certificate to use for encryption. If the certificate has one or more intermediate certificates it must present the entire chain to successfully complete SSL/TLS negotiation. If the complete chain is not presented SSL/TLS communication cannot be established. 
+
+
+
+
+<a name='seealso'></a>
+
+### See also
+
+[Write a plug-in](../../write-plug-in.md) <br /> 
+[Set KeepAlive to false when interacting with external hosts in a plug-in](set-keepalive-false-interacting-external-hosts-plugin.md)<br /> 
+[Set Timeout when making external calls in a plug-in](set-timeout-for-external-calls-from-plug-ins.md)

powerapps-docs/developer/common-data-service/best-practices/index.md

@@ -1,6 +1,6 @@
 ---
 title: "Developers: Best practices and guidance for the Common Data Service | Microsoft Docs"
-description: Best practices and guidance for developers of the Common Data Service in PowerApps.
+description: Best practices and guidance for developers of the Common Data Service in Power Apps.
 services: ''
 suite: powerapps
 documentationcenter: na

powerapps-docs/developer/common-data-service/best-practices/work-with-data/index.md

@@ -1,6 +1,6 @@
 ---
 title: "Developers: Best practices and guidance around working with data for the Common Data Service | Microsoft Docs"
-description: Best practices and guidance around working with data for developers of the Common Data Service in PowerApps.
+description: Best practices and guidance around working with data for developers of the Common Data Service in Power Apps.
 services: ''
 suite: powerapps
 documentationcenter: na

powerapps-docs/developer/common-data-service/best-practices/work-with-metadata/index.md

@@ -1,6 +1,6 @@
 ---
 title: "Developers: Best practices and guidance while working with metadata for the Common Data Service | Microsoft Docs"
-description: Best practices and guidance while working with metadata for developers of the Common Data Service in PowerApps.
+description: Best practices and guidance while working with metadata for developers of the Common Data Service in Power Apps.
 services: ''
 suite: powerapps
 documentationcenter: na