Merge pull request #1746 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/powerapps-docs (branch live)

Author: KumarVivek

powerapps-docs/developer/common-data-service/appendix-app-certification-checklist.md

@@ -40,7 +40,7 @@ The following checklist provides the list of validations performed by Microsoft
 <td>Code Validation</td>
 <td>
 <ul>
-<li>Code validation for Canvas apps will be done through <a href="https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/accessibility-checker">Accessibility Checker tool</a> in PowerApps to check for the following:
+<li>Code validation for Canvas apps will be done through <a href="https://docs.microsoft.com/powerapps/maker/canvas-apps/accessibility-checker">Accessibility Checker tool</a> in PowerApps to check for the following:
 <ul>
 <li>Static formula errors and warnings: If any issues found then certification team will share the feedback to resolve and resubmit to AppSource.</li>
 <li>Runtime errors: May occur once the app is opened in Run mode to view. Any issues found will be reported through email.</li>

powerapps-docs/developer/common-data-service/azure-integration.md

@@ -73,7 +73,7 @@ For more information about the asynchronous service see [Asynchronous service](a
 The service bus relays the request message data context between Common Data Service and Azure Service Bus solution listener applications. The service bus also provides data security so that only authorized applications can access the posted Dynamics 365 data.  Authorization of Common Data Service to post the data context to the service bus and for listener applications to read it is managed by  Azure Shared Access Signatures (SAS).  
 
 
- For more information about the service bus, see [Service Bus](https://azure.microsoft.com/en-us/services/service-bus/). For more information about service bus authorization, see [Service Bus authentication and authorization](https://azure.microsoft.com/en-us/documentation/articles/service-bus-authentication-and-authorization/).  
+ For more information about the service bus, see [Service Bus](https://azure.microsoft.com/services/service-bus/). For more information about service bus authorization, see [Service Bus authentication and authorization](https://azure.microsoft.com/documentation/articles/service-bus-authentication-and-authorization/).  
 
 ### Microsoft Azure Solution
 

powerapps-docs/developer/common-data-service/best-practices/business-logic/set-keepalive-false-interacting-external-hosts-plugin.md

@@ -281,7 +281,7 @@ The following examples show the problematic pattern based on the method you use
 Plug-ins interacting with external services may experience abnormally increased execution times. The problem is due to the ([KeepAlive property](https://msdn.microsoft.com/library/system.net.httpwebrequest.keepalive.aspx)) of HTTP requests issued to external web servers. If the `KeepAlive` property is set to true or not defined at all (default behavior is true) the Sandbox client on the server could continue to try and use a persistent session even though the session has become expired due to network device configuration. The cause of the extended execution time is due to the network retrying the request until the connection is, ultimately, reset.
 
 > [!IMPORTANT]
-> This affects all code that initiates HTTP Requests to a web server using [System.Net.WebClient](https://msdn.microsoft.com/library/system.net.webclient.aspx), [System.Net.WebRequest](https://msdn.microsoft.com/library/system.net.webrequest.aspx) or [System.Net.HttpWebRequest](https://msdn.microsoft.com/library/system.net.httpwebrequest.aspx) as well as Windows Communications Foundation (WCF) client communications using an HTTP transport binding directly or indirectly via [ChannelFactory<TChannel>](https://docs.microsoft.com/dotnet/api/system.servicemodel.channelfactory-1) or [ClientBase<T>](https://docs.microsoft.com/dotnet/api/system.servicemodel.clientbase-1).
+> This affects all code that initiates HTTP Requests to a web server using [System.Net.WebClient](https://msdn.microsoft.com/library/system.net.webclient.aspx), [System.Net.WebRequest](https://msdn.microsoft.com/library/system.net.webrequest.aspx) or [System.Net.HttpWebRequest](https://msdn.microsoft.com/library/system.net.httpwebrequest.aspx) as well as Windows Communications Foundation (WCF) client communications using an HTTP transport binding directly or indirectly via [ChannelFactory\<TChannel>](https://docs.microsoft.com/dotnet/api/system.servicemodel.channelfactory-1) or [ClientBase\<T>](https://docs.microsoft.com/dotnet/api/system.servicemodel.clientbase-1).
 
 This behavior is transparent to end users and traditional logging as the execution is due to network delays.  If the plug-in was registered as a synchronous event, users could experience intermittent performance issues during those registered operations which could cause unresponsiveness of model-driven apps.  If the plug-in is registered asynchronously, the issue would only be observed by reviewing execution times of the plug-in and seeing the execution taking longer than normal or expected.
 

powerapps-docs/developer/common-data-service/create-auto-number-attributes.md

@@ -25,7 +25,7 @@ With Common Data Service, you can add an auto-number attribute for any entity. C
 
 You can create an auto-number attribute in the same way you create a string attribute using the **StringAttributeMetadata** class except that you use the new **AutoNumberFormat** property. Use the **AutoNumberFormat** property to define a pattern that includes sequential numbers and random strings by composing placeholders, which indicates the length and type of values that are generated. The random strings help you to avoid duplicates or collisions, especially when offline clients trying to create auto-numbers.
 
-When creating an auto-number attribute, the **StringAttributeMetadata.FormatName** property or the **StringAttributeMetadata.Format** property values must be Text. Since these are the default values you will typically not set this property. You cannot create an auto-number attribute that uses any other special kind of format such as Email, Phone, TextArea, Url or any other [existing formats](https://msdn.microsoft.com/en-us/library/microsoft.xrm.sdk.metadata.stringformatname.aspx).
+When creating an auto-number attribute, the **StringAttributeMetadata.FormatName** property or the **StringAttributeMetadata.Format** property values must be Text. Since these are the default values you will typically not set this property. You cannot create an auto-number attribute that uses any other special kind of format such as Email, Phone, TextArea, Url or any other [existing formats](https://msdn.microsoft.com/library/microsoft.xrm.sdk.metadata.stringformatname.aspx).
 
 The sequential segment is generated by SQL and hence uniqueness is guaranteed by SQL.
 
@@ -61,7 +61,7 @@ CreateAttributeRequest widgetSerialNumberAttributeRequest = new CreateAttributeR
 
 You can create and update entity definitions using the Web API.
 
-More information: [Create and update entity definitions using the Web API > Create attributes](https://msdn.microsoft.com/en-us/library/mt593078.aspx#Anchor_3).
+More information: [Create and update entity definitions using the Web API > Create attributes](https://msdn.microsoft.com/library/mt593078.aspx#Anchor_3).
 
 #### Request
 ```http
@@ -236,7 +236,7 @@ _serviceProxy.Execute(req);
 ```
 Using the Web API **SetAutoNumberSeed** Action.
 
-More information: [Use Web API actions > Unbound actions](https://msdn.microsoft.com/en-us/library/mt607600.aspx#bkmk_unboundActions)
+More information: [Use Web API actions > Unbound actions](https://msdn.microsoft.com/library/mt607600.aspx#bkmk_unboundActions)
 
 #### Request
 

powerapps-docs/developer/common-data-service/data-export-service.md

@@ -37,11 +37,11 @@ Data Export is an add-on service made available as a Common Data Service solutio
 
 - The subscription must support the volume of data being replicated from your Common Data Service instance.  
 
-- Firewall settings must allow access from the IP address of your  Data Export service. For more information, see [Configure an Azure SQL Database server-level firewall rule using the Azure Portal](https://azure.microsoft.com/en-us/documentation/articles/sql-database-configure-firewall-settings/).  
+- Firewall settings must allow access from the IP address of your  Data Export service. For more information, see [Configure an Azure SQL Database server-level firewall rule using the Azure Portal](https://azure.microsoft.com/documentation/articles/sql-database-configure-firewall-settings/).  
 
 - It is recommended that option “Allow access to azure services” be enabled.  
 
-- The database user, specified in the  data export connection string, must have the proper create and alter permissions on the target database.  At minimum these include: `CRTB`, `CRTY`, `CRVW`,     `CRPR`, and `ALUS`. For more information, see [Permissions (Database Engine)](https://msdn.microsoft.com/en-us/library/ms191291.aspx).  
+- The database user, specified in the  data export connection string, must have the proper create and alter permissions on the target database.  At minimum these include: `CRTB`, `CRTY`, `CRVW`,     `CRPR`, and `ALUS`. For more information, see [Permissions (Database Engine)](https://msdn.microsoft.com/library/ms191291.aspx).  
 
 - At least one user have extensive permissions on the schema. The following script creates such a new user.  
 
@@ -57,7 +57,7 @@ GRANT ALTER, REFERENCES, INSERT, DELETE, UPDATE, SELECT, EXECUTE ON SCHEMA::dbo
 
 ```  
 
-For online solutions and services, Azure provides a [Key Vault](https://azure.microsoft.com/en-us/services/key-vault/) service to safeguard cryptographic keys, passwords, and other secrets.  To use Azure Key Vault, this customer-owned service must be configured so that permission is granted to "Dynamics 365 Data Export Service", which is used to safely store the SQL Azure connection string. To perform this configuration with a PowerShell script, see [How to set up Azure Key Vault](https://technet.microsoft.com/library/mt744592.aspx). Alternately, this service can be managed through its REST API; see [Key Vault management](https://msdn.microsoft.com/library/azure/mt620024.aspx).  
+For online solutions and services, Azure provides a [Key Vault](https://azure.microsoft.com/services/key-vault/) service to safeguard cryptographic keys, passwords, and other secrets.  To use Azure Key Vault, this customer-owned service must be configured so that permission is granted to "Dynamics 365 Data Export Service", which is used to safely store the SQL Azure connection string. To perform this configuration with a PowerShell script, see [How to set up Azure Key Vault](https://technet.microsoft.com/library/mt744592.aspx). Alternately, this service can be managed through its REST API; see [Key Vault management](https://msdn.microsoft.com/library/azure/mt620024.aspx).  
 
 It is also advised that you add the ___domain https://discovery.crmreplication.azure.net/ to the trusted sites list in your browser and to enable pop-ups for this site.  
 
@@ -100,7 +100,7 @@ It is also advised that you add the ___domain https://discovery.crmreplication.azur
 |profiles/{id}/failures|[GET](https://discovery.crmreplication.azure.net/swagger/ui/index#/Profiles/Profiles_GetProfileFailuresInfoById)|Get the connection string to a blob that contains failure details for a given profile|  
 
 ### Gain Access  
-Because only Common Data Service System Administrators are authorized to perform data export operations, these APIs enforce caller authorization through the use of Azure Active Directory ([AAD](https://azure.microsoft.com/en-us/services/active-directory/)) [security tokens](https://azure.microsoft.com/en-us/documentation/articles/active-directory-token-and-claims/). The following code snippet demonstrates generating such a token for a web application by using the administrator's name and password.   You must replace the `AppId`, `crmAdminUser` and `crmAdminPassword` with values appropriate to your service. This approach can be used for development and testing, but more secure means should be used for production, such as the use of Azure Key Vault.  
+Because only Common Data Service System Administrators are authorized to perform data export operations, these APIs enforce caller authorization through the use of Azure Active Directory ([AAD](https://azure.microsoft.com/services/active-directory/)) [security tokens](https://azure.microsoft.com/documentation/articles/active-directory-token-and-claims/). The following code snippet demonstrates generating such a token for a web application by using the administrator's name and password.   You must replace the `AppId`, `crmAdminUser` and `crmAdminPassword` with values appropriate to your service. This approach can be used for development and testing, but more secure means should be used for production, such as the use of Azure Key Vault.  
 
 ```csharp  
 
@@ -119,7 +119,7 @@ using Microsoft.IdentityModel.Clients.ActiveDirectory;
 
 ```  
 
-For instructions on how to obtain a `AppId` see [Authorize access to web applications using OAuth 2.0 and Azure Active Directory](https://azure.microsoft.com/en-us/documentation/articles/active-directory-protocols-oauth-code/). For more information about Azure user security, see [Authentication Scenarios for Azure AD](https://azure.microsoft.com/en-us/documentation/articles/active-directory-authentication-scenarios/).  
+For instructions on how to obtain a `AppId` see [Authorize access to web applications using OAuth 2.0 and Azure Active Directory](https://azure.microsoft.com/documentation/articles/active-directory-protocols-oauth-code/). For more information about Azure user security, see [Authentication Scenarios for Azure AD](https://azure.microsoft.com/documentation/articles/active-directory-authentication-scenarios/).  
   
 ### Error handling and failure processing  
  Once a profile is correctly configured, the synchronization process is typically highly reliable. However, if a record fails to synchronize, the following failure processing is applied:  

powerapps-docs/developer/common-data-service/outlook-client/sample-outlook-methods.md

@@ -17,7 +17,7 @@ search.app:
 ---
 # Sample: Use Dynamics 365 for Outlook methods
 
-This sample code is for Common Data Service. To download the sample, refer [Sample: Use Dynamics 365 for Outlook methods](https://msdn.microsoft.com/en-us/library/gg309513.aspx).
+This sample code is for Common Data Service. To download the sample, refer [Sample: Use Dynamics 365 for Outlook methods](https://msdn.microsoft.com/library/gg309513.aspx).
 
 ## Prerequisites
 

powerapps-docs/developer/common-data-service/plug-ins.md

@@ -83,10 +83,10 @@ These topics provide details that you will use to create plug-ins.
 - [Handle exceptions](handle-exceptions.md)
 - [Register a plug-in](register-plug-in.md)
 - [Debug Plug-ins](debug-plug-in.md)
-- 
+ 
 These topics provide additional information about writing or debugging a plug-in, or analyzing its performance.
 
 - [Impersonate a user](impersonate-a-user.md)
 - [Tracing and logging](logging-tracing.md)
 - [Analyze performance](analyze-performance.md)
-- [Access external web resources](access-web-services.md)]
+- [Access external web resources](access-web-services.md)

powerapps-docs/developer/common-data-service/use-multi-tenant-server-server-authentication.md

@@ -63,9 +63,9 @@ In this scenario any Common Data Service tenant can potentially use your multi-t
 
  Exactly how you do this will not be the focus of this topic. There are a number of ways you can approach this and make choices that fit your requirements or preferences. See the following links for more information and samples:  
 
-- [Build a multi-tenant SaaS web application using Azure AD & OpenID Connect](https://azure.microsoft.com/en-us/documentation/samples/active-directory-dotnet-webapp-multitenant-openidconnect/)  
+- [Build a multi-tenant SaaS web application using Azure AD & OpenID Connect](https://azure.microsoft.com/documentation/samples/active-directory-dotnet-webapp-multitenant-openidconnect/)  
 
-- [Build a multi-tenant SaaS web application that calls a web API using Azure AD](https://azure.microsoft.com/en-us/documentation/samples/active-directory-webapp-webapi-multitenant-openidconnect-aspnetcore/)  
+- [Build a multi-tenant SaaS web application that calls a web API using Azure AD](https://azure.microsoft.com/documentation/samples/active-directory-webapp-webapi-multitenant-openidconnect-aspnetcore/)  
 
   Azure AD requires the following values to register your application:  
 
@@ -86,7 +86,7 @@ In this scenario any Common Data Service tenant can potentially use your multi-t
 
  In the process of creating and registering your application for development you will most likely use `http://localhost` as the **Sign-on URL** and **Reply URL** values so you can test and debug your application locally before publishing. You will need to change these values before you publish your app.  
 
- When you register your app you must generate a key, also known as a `ClientSecret`. These keys can be configured for a 1 or 2-year duration. As the host of the application you must treat this value like a password and it is your responsibility to manage renewal of the keys before they expire. You may want to use Key Vault. More information: [https://azure.microsoft.com/en-us/services/key-vault/](https://azure.microsoft.com/en-us/services/key-vault/)  
+ When you register your app you must generate a key, also known as a `ClientSecret`. These keys can be configured for a 1 or 2-year duration. As the host of the application you must treat this value like a password and it is your responsibility to manage renewal of the keys before they expire. You may want to use Key Vault. More information: [https://azure.microsoft.com/services/key-vault/](https://azure.microsoft.com/services/key-vault/)  
 
 <a name="bkmk_GrantApplicationRights"></a>
 

powerapps-docs/developer/common-data-service/use-single-tenant-server-server-authentication.md

@@ -110,4 +110,4 @@ Shown below is example console output obtained from a D365 organization that onl
 
 [Use Multi-Tenant Server-to-server authentication](use-multi-tenant-server-server-authentication.md)   
 [Build web applications using Server-to-Server (S2S) authentication](build-web-applications-server-server-s2s-authentication.md)  
-[How to: Sign in any Azure Active Directory user using the multi-tenant application pattern](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant)
+[How to: Sign in any Azure Active Directory user using the multi-tenant application pattern](https://docs.microsoft.com/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant)

powerapps-docs/developer/common-data-service/walkthrough-configure-azure-sas-integration.md

@@ -3,8 +3,7 @@ title: "Walkthrough: Configure Microsoft Azure (SAS) for integration (Common Dat
 description: "The walkthrough guides you through configuring the Azure Service Bus issuer, scope, and rules to allow a listener application to read the Common Data Service messages posted to the Azure Service Bus."
 keywords: ""
 ms.date: 10/31/2018
-ms.service:
-  - powerapps
+ms.service: powerapps
 ms.custom:
   - ""
 ms.topic: article
@@ -27,7 +26,7 @@ search.app:
 This walkthrough guides you through configuring the Azure Service Bus issuer, scope, and rules to allow a listener application to read the Common Data Service messages posted to the Azure Service Bus.  
 
 > [!NOTE]
->  This walkthrough applies to any Common Data Service deployment when using SAS authorization for Azure messaging. For more information about Azure Service Bus authorization, see [Service Bus authentication and authorization](https://azure.microsoft.com/en-us/documentation/articles/service-bus-authentication-and-authorization/).  
+>  This walkthrough applies to any Common Data Service deployment when using SAS authorization for Azure messaging. For more information about Azure Service Bus authorization, see [Service Bus authentication and authorization](https://azure.microsoft.com/documentation/articles/service-bus-authentication-and-authorization/).  
 >   
 > You must use the Plug-in Registration Tool. To download the plug-in registration tool, see [Download tools from NuGet](download-tools-NuGet.md).