resolving merge conflict and PR review issues

MashaMSFT · MashaMSFT · commit aed020077b91 · 2019-12-03T17:17:32.000-08:00
diff --git a/docs/big-data-cluster/deploy-active-directory.md b/docs/big-data-cluster/deploy-active-directory.md
@@ -5,7 +5,7 @@ description: Learn how to upgrade SQL Server Big Data Clusters in an Active Dire
 author: NelGson
 ms.author: negust
 ms.reviewer: mikeray
-ms.date: 11/27/2019
+ms.date: 12/02/2019
 ms.topic: conceptual
 ms.prod: sql
 ms.technology: big-data-cluster
@@ -170,13 +170,16 @@ AD integration requires the following parameters. Add these parameters to the `c
 
 - `security.domainDnsName`: Name of your domain (e.g. `contoso.local`).
 
-- `security.clusterAdmins`: This parameter takes **one AD group**. Members of this group will get administrator permissions in the cluster. This means that they will have sysadmin permissions in SQL Server, superuser permissions in HDFS and administrators in Controller. **Please note that this group needs to exist in AD before deployment begins**
+- `security.clusterAdmins`: This parameter takes **one AD group**. Members of this group will get administrator permissions in the cluster. This means that they will have sysadmin permissions in SQL Server, superuser permissions in HDFS and administrators in Controller. **Please note that this group needs to exist in AD before deployment begins. Also note that this group can not be DomainLocal scoped in Active Directory. A domain local scoped group will result in deployment failure.**
 
-- `security.clusterUsers`: List of the AD groups that are regular users (no administrator permissions) in the big data cluster. **Please note that these groups need to exist in AD before deployment begins**
+- `security.clusterUsers`: List of the AD groups that are regular users (no administrator permissions) in the big data cluster. **Please note that these groups need to exist in AD before deployment begins. Also note that these groups can not be DomainLocal scoped in Active Directory. A domain local scoped group will result in deployment failure.**
 
-- `security.appOwners` **Optional parameter**: List of the AD groups who have permissions to create, delete, and run any application. **Please note that these groups need to exist in AD before deployment begins**
+- `security.appOwners` **Optional parameter**: List of the AD groups who have permissions to create, delete, and run any application. **Please note that these groups need to exist in AD before deployment begins. Also note that these groups can not be DomainLocal scoped in Active Directory. A domain local scoped group will result in deployment failure.**
 
-- `security.appReaders` **Optional parameter**: list of the AD groups who have permissions to run any application. **Please note that these groups need to exist in AD before deployment begins**
+- `security.appReaders` **Optional parameter**: list of the AD groups who have permissions to run any application. **Please note that these groups need to exist in AD before deployment begins. Also note that these groups can not be DomainLocal scoped in Active Directory. A domain local scoped group will result in deployment failure.**
+
+**How to check AD group scope:**
+[Click here for instructions](https://docs.microsoft.com/en-us/powershell/module/activedirectory/get-adgroup?view=winserver2012-ps&viewFallbackFrom=winserver2012r2-ps) for checking the scope of an AD group, to determine if it is DomainLocal.
 
 If you have not already initialized the deployment configuration file, you can run this command to get a copy of the configuration.
 
@@ -290,3 +293,5 @@ curl -k -v --negotiate -u : https://<Gateway DNS name>:30443/gateway/default/web
 - The secure AD mode will only work on `kubeadm` deployment environments and not on AKS right now. The `kubeadm-prod` deployment profile includes the security sections by default.
 
 - Only one BDC per domain is allowed at this time. Enabling multiple BDCs per domain is planned for a future release.
+
+- None of the AD groups specified in security configurations can be DomainLocal scoped. You can check the scope of an AD group by following [these instructions](https://docs.microsoft.com/en-us/powershell/module/activedirectory/get-adgroup?view=winserver2012-ps&viewFallbackFrom=winserver2012r2-ps).
diff --git a/docs/docfx.json b/docs/docfx.json
@@ -128,8 +128,8 @@
         "2014/**/*.md": "SQL Server 2014",
         "2014/integration-services/**/*.md": "SQL Server 2014 Integration Services",
         "2014/relational-database/replication/**/*.md": "SQL Server 2014 Replication",
-        "2014/reporting-services/**/*.md": "SQL Server 2014 Reporting Services",
-        "2014/database-engine/availability-groups/**/*.md": "SQL Server 2014 Always On",
+        "2014/reporting-services/**/*.md": "SQL Server 2014 Reporting Services (SSRS)",
+        "2014/database-engine/availability-groups/windows/**/*.md": "SQL Server 2014 Always On",
         "2014/sql-server/failover-clusters/**/*.md": "SQL Server 2014 Always On",
         "2014/database-engine/database-mirroring/**/*.md": "SQL Server 2014 Database Mirroring",
         "2014/database-engine/log-shipping/windows/**/*.md": "SQL Server 2014 Log Shipping",
diff --git a/docs/relational-databases/system-catalog-views/sys-database-principals-transact-sql.md b/docs/relational-databases/system-catalog-views/sys-database-principals-transact-sql.md
@@ -45,7 +45,8 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 |**allow_encrypted_value_modifications**|**bit**|**Applies to**: [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] and later, [!INCLUDE[ssSDS_md](../../includes/sssds-md.md)].<br /><br /> Suppresses cryptographic metadata checks on the server in bulk copy operations. This enables the user to bulk copy data encrypted using Always Encrypted, between tables or databases, without decrypting the data. The default is OFF. |      
   
 ## Remarks  
- The *PasswordLastSetTime* properties are available on all supported configurations of SQL Server, but the other properties are only available when SQL Server is running on Windows Server 2003 or later and both CHECK_POLICY and CHECK_EXPIRATION are enabled. See [Password Policy](../../relational-databases/security/password-policy.md) for more information.  
+ The *PasswordLastSetTime* properties are available on all supported configurations of SQL Server, but the other properties are only available when SQL Server is running on Windows Server 2003 or later and both CHECK_POLICY and CHECK_EXPIRATION are enabled. See [Password Policy](../../relational-databases/security/password-policy.md) for more information.
+The values of the principal_id may be reused in the case that principals have been dropped and therefore is not guaranteed to be ever-increasing.
   
 ## Permissions  
  Any user can see their own user name, the system users, and the fixed database roles. To see other users, requires ALTER ANY USER, or a permission on the user. To see user-defined roles, requires ALTER ANY ROLE, or membership in the role.  
diff --git a/docs/reporting-services/application-integration/choosing-between-url-access-and-soap.md b/docs/reporting-services/application-integration/choosing-between-url-access-and-soap.md
@@ -1,17 +1,18 @@
 ---
-title: "Choosing between URL access and SOAP in Reporting Services | Microsoft Docs"
+title: "Choose between URL access and SOAP"
+description: "There are two ways to integrate Reporting Services into custom applications: URL access and the Reporting Services SOAP API. Which to use depends on several factors."
 ms.date: 10/19/2017
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: application-integration
 
-
+ms.custom: seo-lt-2019
 ms.topic: reference
 author: maggiesMSFT
 ms.author: maggies
 monikerRange: "= sql-server-2016 || = sqlallproducts-allversions"
 ---
-# Choosing between URL access and SOAP in Reporting Services
+# Choose between URL access and SOAP in Reporting Services
 
 [!INCLUDE [ssrs-appliesto](../../includes/ssrs-appliesto.md)] [!INCLUDE[ssrs-appliesto-2016](../../includes/ssrs-appliesto-2016.md)] [!INCLUDE[ssrs-appliesto-not-2017](../../includes/ssrs-appliesto-not-2017.md)] [!INCLUDE [ssrs-appliesto-not-pbirs](../../includes/ssrs-appliesto-not-pbirs.md)]
 
diff --git a/docs/reporting-services/application-integration/integrating-reporting-services-into-applications.md b/docs/reporting-services/application-integration/integrating-reporting-services-into-applications.md
@@ -1,5 +1,7 @@
 ---
-title: "Integrating Reporting Services into Applications | Microsoft Docs"
+title: "Integrating into Applications"
+description: Reporting Services is an open and extensible reporting platform designed to provide developers with a comprehensive set of APIs for developing solutions.
+ms.custom: seo-lt-2019
 ms.date: 05/14/2019
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
diff --git a/docs/reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls-data-collection.md b/docs/reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls-data-collection.md
@@ -1,7 +1,9 @@
 ---
-title: Data collection in ReportViewer Control 2016
+title: Data collection in ReportViewer Control
+description: Anonymous usage data is collected by the control to better understand how customers use the product. Usage data enables future development to focus on improvements that are most relevant to customers.
 author: maggiesMSFT
 ms.author: maggies
+ms.custom: seo-lt-2019
 ms.reviewer: ""
 ms.prod: reporting-services
 ms.prod_service: reporting-services-native
@@ -10,7 +12,7 @@ ms.topic: reference
 ms.custom: ""
 ms.date: 09/18/2018
 ---
-# Integrating Reporting Services Using ReportViewer Controls - Data Collection
+# Integrate Reporting Services Using ReportViewer Controls - Data Collection
 
 Anonymous usage data is collected by the control to better understand how customers make use of the product. Usage data enables future development to be focused on improvements that are most relevant to customers.
 
diff --git a/docs/reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls-get-started.md b/docs/reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls-get-started.md
@@ -1,5 +1,7 @@
 ---
-title: "Getting started with the ReportViewer 2016 control | Microsoft Docs"
+title: "Get started with Report Viewer controls"
+description: The Report Viewer controls can be used to integrate Reporting Services RDL reports into WebForms and WinForms apps. 
+ms.custom: seo-lt-2019
 ms.date: 09/18/2018
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
diff --git a/docs/reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls.md b/docs/reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls.md
@@ -1,10 +1,11 @@
 ---
-title: "Integrating Reporting Services Using the Report Viewer Controls | Microsoft Docs"
+title: "Integrate Using Report Viewer Controls"
+description: Visual Studio provides two Report Viewer controls for integrating report viewing functionality into your applications. 
 ms.date: 09/18/2018
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: application-integration
-
+ms.custom: seo-lt-2019
 
 ms.topic: reference
 helpviewer_keywords: 
@@ -14,7 +15,7 @@ ms.assetid: 3ba47fb4-73a9-4059-89fd-329adebe94a8
 author: maggiesMSFT
 ms.author: maggies
 ---
-# Integrating Reporting Services Using Report Viewer Controls
+# Integrate Reporting Services Using Report Viewer Controls
   [!INCLUDE[msCoName](../../includes/msconame-md.md)] Visual Studio 2015 provides two Report Viewer controls for integrating report viewing functionality into your applications. There is a version for Windows Forms-based applications and one for Web Forms applications. Each control provides similar functionality but each is designed to target their individual environments. Both controls can process reports that have been deployed to a report server (remote processing mode) or have been copied to a computer where [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] has not been installed (local processing mode).  
   
  The Report Viewer control does not include built-in support for dynamically adapting to different devices with different screen resolutions.  
diff --git a/docs/reporting-services/application-integration/integrating-reporting-services-using-soap-web-application.md b/docs/reporting-services/application-integration/integrating-reporting-services-using-soap-web-application.md
@@ -1,11 +1,12 @@
 ---
-title: "Using the SOAP API in a Web Application - Reporting Services | Microsoft Docs"
+title: "Use SOAP API in Web Applications"
+description: You can access the full functionality of the report server through the Reporting Services SOAP API.
 ms.date: 06/26/2019
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: application-integration
 
-
+ms.custom: seo-lt-2019
 ms.topic: reference
 helpviewer_keywords: 
   - "SOAP [Reporting Services], Web applications"
diff --git a/docs/reporting-services/application-integration/integrating-reporting-services-using-soap-windows-application.md b/docs/reporting-services/application-integration/integrating-reporting-services-using-soap-windows-application.md
@@ -1,11 +1,12 @@
 ---
-title: "Using the SOAP API in a Windows Application | Microsoft Docs"
+title: "Use SOAP API in Windows Applications"
+description: You can access the full functionality of the report server through the Reporting Services SOAP API. Access the Web service in a Windows application by writing code that makes calls to the service. 
 ms.date: 03/14/2017
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: application-integration
 
-
+ms.custom: seo-lt-2019
 ms.topic: reference
 helpviewer_keywords: 
   - "rendered reports [Reporting Services]"
diff --git a/docs/reporting-services/application-integration/integrating-reporting-services-using-soap.md b/docs/reporting-services/application-integration/integrating-reporting-services-using-soap.md
@@ -1,11 +1,12 @@
 ---
-title: "Integrating Reporting Services Using SOAP | Microsoft Docs"
+title: "Integrate Using SOAP"
+description: The Reporting Services SOAP API provides several Web service endpoints for developing custom reporting solutions. 
 ms.date: 03/14/2017
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: application-integration
 
-
+ms.custom: seo-lt-2019
 ms.topic: reference
 helpviewer_keywords: 
   - "Report Server Web service, application integration"
diff --git a/docs/reporting-services/application-integration/integrating-reporting-services-using-url-access-web-application.md b/docs/reporting-services/application-integration/integrating-reporting-services-using-url-access-web-application.md
@@ -1,10 +1,11 @@
 ---
-title: "Using URL Access in a Web Application | Microsoft Docs"
+title: "Use URL Access in Web Applications"
+description: URL access in Reporting Services is specifically designed to enable access to individual reports over a network. 
 ms.date: 03/16/2017
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: application-integration
-
+ms.custom: seo-lt-2019
 
 ms.topic: reference
 helpviewer_keywords: 
diff --git a/docs/reporting-services/application-integration/integrating-reporting-services-using-url-access-windows-application.md b/docs/reporting-services/application-integration/integrating-reporting-services-using-url-access-windows-application.md
@@ -1,11 +1,12 @@
 ---
-title: "Using URL Access in a Windows Application | Microsoft Docs"
+title: "Use URL Access in Windows Applications"
+description: URL access to a report server is optimized for a Web environment, but you can also use URL access to embed Reporting Services reports in a Windows application.
 ms.date: 03/14/2017
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: application-integration
 
-
+ms.custom: seo-lt-2019
 ms.topic: reference
 helpviewer_keywords: 
   - "Windows applications [Reporting Services]"
diff --git a/docs/reporting-services/application-integration/integrating-reporting-services-using-url-access.md b/docs/reporting-services/application-integration/integrating-reporting-services-using-url-access.md
@@ -1,10 +1,11 @@
 ---
-title: "Integrating Reporting Services Using URL Access | Microsoft Docs"
+title: "Integrate Using URL Access"
+description: A URL request enables you to access a specific report server as well as the reports, resources, and other items in the report server database.
 ms.date: 03/14/2017
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: application-integration
-
+ms.custom: seo-lt-2019
 
 ms.topic: reference
 helpviewer_keywords: 
@@ -14,7 +15,7 @@ ms.assetid: f1014f7d-fafa-4aa8-8bd2-5bdba835d9b6
 author: maggiesMSFT
 ms.author: maggies
 ---
-# Integrating Reporting Services Using URL Access
+# Integrate Reporting Services Using URL Access
   With URL access, you access reports through a report server URL. A URL request enables you to access a specific report server as well as the reports, resources, and other items in the report server database. You can also customize the report viewing and navigation experience for your users. The query string of the URL contains device information settings, as well as report parameters targeted at your report and the chosen rendering output. The way the report server handles URL requests depends on the parameters, parameter prefixes, and type of item that you are accessing through the URL.  
   
  You can use URL access to embed hyperlinks to reports and other report server items in the applications that you develop, whether in a Windows or Web environment.  
diff --git a/docs/reporting-services/application-integration/release-notes-ssrs-application-integration.md b/docs/reporting-services/application-integration/release-notes-ssrs-application-integration.md
@@ -1,17 +1,19 @@
 ---
-title: "Release Notes for the Report Viewer controls of SSRS"
+title: "Release Notes for Report Viewer controls"
+description: The release notes for the Report Viewer controls of WebForms and WinForms, related to Reporting Services.
 ms.date: 09/20/2018
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: application-integration
+ms.custom: seo-lt-2019
 
 ms.topic: reference
 ms.assetid: 112e0240-351d-46a9-98c7-2be09f26ac60
 ms.reviewer: maggies
 author: RhysSchmidtke
 ms.author: rhys
 ---
-# Release Notes for the Report Viewer controls for WebForms and WinForms of SSRS
+# Release Notes for Report Viewer controls for WebForms and WinForms of SSRS
 
 These are the release notes for the Report Viewer controls of WebForms and WinForms, related to [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] (SSRS).
 
diff --git a/docs/reporting-services/application-integration/reportviewer-controls-support.md b/docs/reporting-services/application-integration/reportviewer-controls-support.md
@@ -1,6 +1,8 @@
 ---
-title: Support for Report Viewer current branch versions
+title: Support for Report Viewer control versions
+description: The Microsoft Report Viewer control is compatible with SQL Server Reporting Services and Power BI Report Server that follow the Microsoft modern support lifecycle policy.
 author: maggiesMSFT
+ms.custom: seo-lt-2019
 ms.author: maggies
 ms.reviewer: jonhp
 ms.prod: reporting-services
diff --git a/docs/reporting-services/application-integration/using-the-webforms-reportviewer-control.md b/docs/reporting-services/application-integration/using-the-webforms-reportviewer-control.md
@@ -1,10 +1,11 @@
 ---
-title: "Using the WebForms ReportViewer Control | Microsoft Docs"
+title: "Use WebForms ReportViewer Control"
+description: To view reports deployed to a report server or reports that exist on the local file system, you can use the WebForms ReportViewer control to render them in a Web application.
 ms.date: 06/12/2017
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: application-integration
-
+ms.custom: seo-lt-2019
 
 ms.topic: reference
 helpviewer_keywords: 
@@ -13,7 +14,7 @@ ms.assetid: 4c200f36-4012-4108-8095-370b426ccf8d
 author: maggiesMSFT
 ms.author: maggies
 ---
-# Using the WebForms ReportViewer Control
+# Use the WebForms ReportViewer Control
   To view reports deployed to a report server or reports that exist on the local file system, you can use the WebForms ReportViewer control to render them in a Web application.  
   
 ## To use the ReportViewer Control in a Web application  
diff --git a/docs/reporting-services/application-integration/using-the-winforms-reportviewer-control.md b/docs/reporting-services/application-integration/using-the-winforms-reportviewer-control.md
@@ -1,10 +1,11 @@
 ---
-title: "Using the WinForms ReportViewer Control | Microsoft Docs"
+title: "Use WinForms ReportViewer Control"
+description: To view reports that have been deployed to a report server or reports that exist on the local file system, you can use the WinForms ReportViewer control to render them in a Windows application.
 ms.date: 09/06/2016
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: application-integration
-
+ms.custom: seo-lt-2019
 
 ms.topic: reference
 helpviewer_keywords: 
@@ -13,7 +14,7 @@ ms.assetid: 29fb9f7d-ba65-49fd-9cbc-4c380869de96
 author: maggiesMSFT
 ms.author: maggies
 ---
-# Using the WinForms ReportViewer Control
+# Use the WinForms ReportViewer Control
   To view reports that have been deployed to a report server or reports that exist on the local file system, you can use the WinForms ReportViewer control to render them in a Windows application.  
   
 ## To add the ReportViewer Control to a Windows application  
