added/updated ms.workload metadata values

Author: iRaindrop

docs/relational-databases/replication/security/identity-and-access-control-replication.md

@@ -19,34 +19,35 @@ caps.latest.revision: 8
 author: "BYHAM"
 ms.author: "rickbyh"
 manager: "jhubbard"
+ms.workload: "Inactive"
 ---
 # Identity and Access Control (Replication)
-  Authentication is the process by which an entity (typically a computer in this context) verifies that another entity, also called a *principal*, (typically another computer or user) is who or what it claims to be. Authorization is the process by which an authenticated principal is given access to resources, such as a file in the file system, or a table in a database.  
-  
- Replication security uses authentication and authorization to control access to replicated database objects and to the computers and agents involved in replication processing. This is accomplished through three mechanisms:  
-  
--   Agent security  
-  
-     The replication agent security model allows fine-grained control over the accounts under which replication agents run and make connections. For detailed information about the agent security model, see [Replication Agent Security Model](../../../relational-databases/replication/security/replication-agent-security-model.md). For information about setting logins and passwords for agents, see [Manage Logins and Passwords in Replication](../../../relational-databases/replication/security/manage-logins-and-passwords-in-replication.md).  
-  
--   Administration roles  
-  
-     Ensure that the correct server and database roles are used for replication setup, maintenance, and processing. For more information, see [Security Role Requirements for Replication](../../../relational-databases/replication/security/security-role-requirements-for-replication.md).  
-  
--   The publication access list (PAL)  
-  
-     Grant access to publications through the PAL. The PAL functions similarly to a [!INCLUDE[msCoName](../../../includes/msconame-md.md)] Windows access control list. When a Subscriber connects to the Publisher or Distributor and requests access to a publication, the authentication information passed by the agent is checked against the PAL. For more information and best practices for the PAL, see [Secure the Publisher](../../../relational-databases/replication/security/secure-the-publisher.md).  
-  
-## Filtering Published Data  
- In addition to using authentication and authorization to control access to replicated data and objects, replication includes two options to control what data is available at a Subscriber: column filtering and row filtering. For more information about filtering, see [Filter Published Data](../../../relational-databases/replication/publish/filter-published-data.md).  
-  
- When you define an article, you can publish only those columns that are necessary for the publication, and omit those that are unnecessary or contain sensitive data. For example, when publishing the **Customer** table from the Adventure Works database to sales representatives in the field, you can omit the **AnnualSales** column, which might be relevant only to executives at the company.  
-  
- Filtering published data allows you to restrict access to data and allows you to specify the data that is available at the Subscriber. For example, you can filter the **Customer** table so that corporate partners only receive information about those customers whose **ShareInfo** column has a value of "yes." For merge replication, there are security considerations if you use a parameterized filter that includes HOST_NAME(). For more, see the section "Filtering with HOST_NAME()" in [Parameterized Row Filters](../../../relational-databases/replication/merge/parameterized-filters-parameterized-row-filters.md).  
-  
-## See Also  
- [Security and Protection (Replication)](../../../relational-databases/replication/security/security-and-protection-replication.md)   
- [Security Overview (Replication)](../../../relational-databases/replication/security/security-overview-replication.md)   
- [Threat and Vulnerability Mitigation (Replication)](../../../relational-databases/replication/security/threat-and-vulnerability-mitigation-replication.md)  
-  
-  
+  Authentication is the process by which an entity (typically a computer in this context) verifies that another entity, also called a *principal*, (typically another computer or user) is who or what it claims to be. Authorization is the process by which an authenticated principal is given access to resources, such as a file in the file system, or a table in a database.  
+  
+ Replication security uses authentication and authorization to control access to replicated database objects and to the computers and agents involved in replication processing. This is accomplished through three mechanisms:  
+  
+-   Agent security  
+  
+     The replication agent security model allows fine-grained control over the accounts under which replication agents run and make connections. For detailed information about the agent security model, see [Replication Agent Security Model](../../../relational-databases/replication/security/replication-agent-security-model.md). For information about setting logins and passwords for agents, see [Manage Logins and Passwords in Replication](../../../relational-databases/replication/security/manage-logins-and-passwords-in-replication.md).  
+  
+-   Administration roles  
+  
+     Ensure that the correct server and database roles are used for replication setup, maintenance, and processing. For more information, see [Security Role Requirements for Replication](../../../relational-databases/replication/security/security-role-requirements-for-replication.md).  
+  
+-   The publication access list (PAL)  
+  
+     Grant access to publications through the PAL. The PAL functions similarly to a [!INCLUDE[msCoName](../../../includes/msconame-md.md)] Windows access control list. When a Subscriber connects to the Publisher or Distributor and requests access to a publication, the authentication information passed by the agent is checked against the PAL. For more information and best practices for the PAL, see [Secure the Publisher](../../../relational-databases/replication/security/secure-the-publisher.md).  
+  
+## Filtering Published Data  
+ In addition to using authentication and authorization to control access to replicated data and objects, replication includes two options to control what data is available at a Subscriber: column filtering and row filtering. For more information about filtering, see [Filter Published Data](../../../relational-databases/replication/publish/filter-published-data.md).  
+  
+ When you define an article, you can publish only those columns that are necessary for the publication, and omit those that are unnecessary or contain sensitive data. For example, when publishing the **Customer** table from the Adventure Works database to sales representatives in the field, you can omit the **AnnualSales** column, which might be relevant only to executives at the company.  
+  
+ Filtering published data allows you to restrict access to data and allows you to specify the data that is available at the Subscriber. For example, you can filter the **Customer** table so that corporate partners only receive information about those customers whose **ShareInfo** column has a value of "yes." For merge replication, there are security considerations if you use a parameterized filter that includes HOST_NAME(). For more, see the section "Filtering with HOST_NAME()" in [Parameterized Row Filters](../../../relational-databases/replication/merge/parameterized-filters-parameterized-row-filters.md).  
+  
+## See Also  
+ [Security and Protection (Replication)](../../../relational-databases/replication/security/security-and-protection-replication.md)   
+ [Security Overview (Replication)](../../../relational-databases/replication/security/security-overview-replication.md)   
+ [Threat and Vulnerability Mitigation (Replication)](../../../relational-databases/replication/security/threat-and-vulnerability-mitigation-replication.md)  
+  
+  

docs/relational-databases/replication/security/manage-logins-and-passwords-in-replication.md

@@ -20,13 +20,14 @@ caps.latest.revision: 35
 author: "BYHAM"
 ms.author: "rickbyh"
 manager: "jhubbard"
+ms.workload: "Inactive"
 ---
 # Manage Logins and Passwords in Replication
-  Specify the logins and passwords for replication agents when you configure replication. After configuring replication, you can change logins and passwords. For more information, see [View and Modify Replication Security Settings](../../../relational-databases/replication/security/view-and-modify-replication-security-settings.md). If you change the password for an account used by a replication agent, execute [sp_changereplicationserverpasswords (Transact-SQL)](../../../relational-databases/system-stored-procedures/sp-changereplicationserverpasswords-transact-sql.md).  
-  
-## See Also  
- [Replication Agent Security Model](../../../relational-databases/replication/security/replication-agent-security-model.md)   
- [Replication Security Best Practices](../../../relational-databases/replication/security/replication-security-best-practices.md)   
- [Security and Protection (Replication)](../../../relational-databases/replication/security/security-and-protection-replication.md)  
-  
-  
+  Specify the logins and passwords for replication agents when you configure replication. After configuring replication, you can change logins and passwords. For more information, see [View and Modify Replication Security Settings](../../../relational-databases/replication/security/view-and-modify-replication-security-settings.md). If you change the password for an account used by a replication agent, execute [sp_changereplicationserverpasswords (Transact-SQL)](../../../relational-databases/system-stored-procedures/sp-changereplicationserverpasswords-transact-sql.md).  
+  
+## See Also  
+ [Replication Agent Security Model](../../../relational-databases/replication/security/replication-agent-security-model.md)   
+ [Replication Security Best Practices](../../../relational-databases/replication/security/replication-security-best-practices.md)   
+ [Security and Protection (Replication)](../../../relational-databases/replication/security/security-and-protection-replication.md)  
+  
+  

docs/relational-databases/replication/security/manage-logins-in-the-publication-access-list.md

@@ -20,58 +20,59 @@ caps.latest.revision: 45
 author: "BYHAM"
 ms.author: "rickbyh"
 manager: "jhubbard"
+ms.workload: "Inactive"
 ---
 # Manage Logins in the Publication Access List
-  This topic describes how to manage logins in the Publication Access List in [!INCLUDE[ssCurrent](../../../includes/sscurrent-md.md)] by using [!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)] or [!INCLUDE[tsql](../../../includes/tsql-md.md)]. Access to a publication is controlled by the publication access list (PAL). Logins and groups can be added and removed from the PAL.  
-  
- **In This Topic**  
-  
--   **Before you begin:**  
-  
-     [Prerequisites](#Prerequisites)  
-  
--   **To manage logins in the Publication Access List, using:**  
-  
-     [SQL Server Management Studio](#SSMSProcedure)  
-  
-     [Transact-SQL](#TsqlProcedure)  
-  
-##  <a name="BeforeYouBegin"></a> Before You Begin  
-  
-###  <a name="Prerequisites"></a> Prerequisites  
-  
--   You must associate the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] login with a database user in the publication database before you add the login to the PAL.  
-  
-##  <a name="SSMSProcedure"></a> Using SQL Server Management Studio  
- You use the publication access list (PAL) on the **Publication Access List** page of the **Publication Properties - \<Publication>** dialog box to manage logins. For more information about how to access this dialog box, see [View and Modify Publication Properties](../../../relational-databases/replication/publish/view-and-modify-publication-properties.md).  
-  
-#### To manage logins in the PAL  
-  
-1.  On the **Publication Access List** page of the **Publication Properties - \<Publication>** dialog box, use the **Add**, **Remove**, and **Remove All** buttons to add and remove logins and groups from the PAL. Do not remove **distributor_admin** from the PAL. This account is used by replication.  
-  
-    > [!NOTE]  
-    >  If a remote Distributor is used, accounts in the PAL must be available at both the Publisher and the Distributor. The account must be either a domain account or a local account that is defined at both servers. The passwords that are associated with both logins must be the same.  
-  
-2.  [!INCLUDE[clickOK](../../../includes/clickok-md.md)]  
-  
-##  <a name="TsqlProcedure"></a> Using Transact-SQL  
-  
-#### To view groups and logins that belong to the PAL  
-  
-1.  At the Publisher on the publication database, execute [sp_help_publication_access](../../../relational-databases/system-stored-procedures/sp-help-publication-access-transact-sql.md). For **@publication**, specify the publication name. This displays information about the groups and logins in the PAL.  
-  
-#### To add groups and logins to the PAL  
-  
-1.  At the Publisher on the publication database, execute [sp_grant_publication_access](../../../relational-databases/system-stored-procedures/sp-grant-publication-access-transact-sql.md). For **@publication**, specify the publication name; and for **@login**, specify the name of the login or group that is being added.  
-  
-#### To remove groups and logins from the PAL  
-  
-1.  At the Publisher on the publication database, execute [sp_revoke_publication_access](../../../relational-databases/system-stored-procedures/sp-revoke-publication-access-transact-sql.md). For **@publication**, specify the publication name; and for **@login**, specify the name of the login or group that is being removed.  
-  
-## See Also  
- [Manage Logins in the Publication Access List](../../../relational-databases/replication/security/manage-logins-in-the-publication-access-list.md)   
- [Replication Agent Security Model](../../../relational-databases/replication/security/replication-agent-security-model.md)   
- [Secure a Replication Topology](../../../relational-databases/replication/security/secure-a-replication-topology.md)   
- [Secure the Publisher](../../../relational-databases/replication/security/secure-the-publisher.md)  
-  
-  
+  This topic describes how to manage logins in the Publication Access List in [!INCLUDE[ssCurrent](../../../includes/sscurrent-md.md)] by using [!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)] or [!INCLUDE[tsql](../../../includes/tsql-md.md)]. Access to a publication is controlled by the publication access list (PAL). Logins and groups can be added and removed from the PAL.  
+  
+ **In This Topic**  
+  
+-   **Before you begin:**  
+  
+     [Prerequisites](#Prerequisites)  
+  
+-   **To manage logins in the Publication Access List, using:**  
+  
+     [SQL Server Management Studio](#SSMSProcedure)  
+  
+     [Transact-SQL](#TsqlProcedure)  
+  
+##  <a name="BeforeYouBegin"></a> Before You Begin  
+  
+###  <a name="Prerequisites"></a> Prerequisites  
+  
+-   You must associate the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] login with a database user in the publication database before you add the login to the PAL.  
+  
+##  <a name="SSMSProcedure"></a> Using SQL Server Management Studio  
+ You use the publication access list (PAL) on the **Publication Access List** page of the **Publication Properties - \<Publication>** dialog box to manage logins. For more information about how to access this dialog box, see [View and Modify Publication Properties](../../../relational-databases/replication/publish/view-and-modify-publication-properties.md).  
+  
+#### To manage logins in the PAL  
+  
+1.  On the **Publication Access List** page of the **Publication Properties - \<Publication>** dialog box, use the **Add**, **Remove**, and **Remove All** buttons to add and remove logins and groups from the PAL. Do not remove **distributor_admin** from the PAL. This account is used by replication.  
+  
+    > [!NOTE]  
+    >  If a remote Distributor is used, accounts in the PAL must be available at both the Publisher and the Distributor. The account must be either a domain account or a local account that is defined at both servers. The passwords that are associated with both logins must be the same.  
+  
+2.  [!INCLUDE[clickOK](../../../includes/clickok-md.md)]  
+  
+##  <a name="TsqlProcedure"></a> Using Transact-SQL  
+  
+#### To view groups and logins that belong to the PAL  
+  
+1.  At the Publisher on the publication database, execute [sp_help_publication_access](../../../relational-databases/system-stored-procedures/sp-help-publication-access-transact-sql.md). For **@publication**, specify the publication name. This displays information about the groups and logins in the PAL.  
+  
+#### To add groups and logins to the PAL  
+  
+1.  At the Publisher on the publication database, execute [sp_grant_publication_access](../../../relational-databases/system-stored-procedures/sp-grant-publication-access-transact-sql.md). For **@publication**, specify the publication name; and for **@login**, specify the name of the login or group that is being added.  
+  
+#### To remove groups and logins from the PAL  
+  
+1.  At the Publisher on the publication database, execute [sp_revoke_publication_access](../../../relational-databases/system-stored-procedures/sp-revoke-publication-access-transact-sql.md). For **@publication**, specify the publication name; and for **@login**, specify the name of the login or group that is being removed.  
+  
+## See Also  
+ [Manage Logins in the Publication Access List](../../../relational-databases/replication/security/manage-logins-in-the-publication-access-list.md)   
+ [Replication Agent Security Model](../../../relational-databases/replication/security/replication-agent-security-model.md)   
+ [Secure a Replication Topology](../../../relational-databases/replication/security/secure-a-replication-topology.md)   
+ [Secure the Publisher](../../../relational-databases/replication/security/secure-the-publisher.md)  
+  
+