Merge pull request #107332 from CarlRabeler/1672446-C

new pr

Author: Jak-MS

.openpublishing.redirection.json

@@ -32814,6 +32814,11 @@
       "redirect_url": "/azure/role-based-access-control/built-in-roles",
       "redirect_document_id": true
     },
+    {
+      "source_path": "articles/sql-database/sql-database-control-access.md",
+      "redirect_url": "/azure/sql-database/sql-database-manage-logins",
+      "redirect_document_id": true
+    },
     {
       "source_path": "articles/active-directory/role-based-access-control-access-change-history-report.md",
       "redirect_url": "/azure/role-based-access-control/change-history-report",

articles/security/fundamentals/database-security-checklist.md

@@ -24,20 +24,20 @@ To help improve security, Azure Database includes a number of built-in security
 
 These include:
 
--	A firewall that enables you to create [firewall rules](../../sql-database/sql-database-firewall-configure.md) limiting connectivity by IP address,
--	Server-level firewall accessible from the Azure portal
--	Database-level firewall rules accessible from SSMS
--	Secure connectivity to your database using secure connection strings
--	Use access management
--	Data encryption
--	SQL Database auditing
--	SQL Database threat detection
+-    A firewall that enables you to create [firewall rules](../../sql-database/sql-database-firewall-configure.md) limiting connectivity by IP address,
+-    Server-level firewall accessible from the Azure portal
+-    Database-level firewall rules accessible from SSMS
+-    Secure connectivity to your database using secure connection strings
+-    Use access management
+-    Data encryption
+-    SQL Database auditing
+-    SQL Database threat detection
 
 ## Introduction
 Cloud computing requires new security paradigms that are unfamiliar to many application users, database administrators, and programmers. As a result, some organizations are hesitant to implement a cloud infrastructure for data management due to perceived security risks. However, much of this concern can be alleviated through a better understanding of the security features built into Microsoft Azure and Microsoft Azure SQL Database.
 
 ## Checklist
-We recommend that you read the [Azure Database Security Best Practices](database-best-practices.md)  article prior to reviewing this checklist. You will be able to get the most out of this checklist after you understand the best practices. You can then use this checklist to make sure that you’ve addressed the important issues in Azure database security.
+We recommend that you read the [Azure Database Security Best Practices](database-best-practices.md)  article prior to reviewing this checklist. You will be able to get the most out of this checklist after you understand the best practices. You can then use this checklist to make sure that you've addressed the important issues in Azure database security.
 
 
 |Checklist Category| Description|
@@ -46,11 +46,11 @@ We recommend that you read the [Azure Database Security Best Practices](database
 | <br> Encryption in Motion/Transit| <ul><li>[Transport Layer Security](https://docs.microsoft.com/windows-server/security/tls/transport-layer-security-protocol), for data encryption when data is moving to the networks.</li><li>Database requires secure communication from clients based on the [TDS(Tabular Data Stream)](https://msdn.microsoft.com/library/dd357628.aspx) protocol over TLS (Transport Layer Security).</li></ul> |
 |<br>Encryption at rest| <ul><li>[Transparent Data Encryption](https://go.microsoft.com/fwlink/?LinkId=526242), when inactive data is stored physically in any digital form.</li></ul>|
 |**Control Access**||  
-|<br> Database Access | <ul><li>[Authentication](../../sql-database/sql-database-control-access.md) (Azure Active Directory Authentication) AD authentication uses identities managed by Azure Active Directory.</li><li>[Authorization](../../sql-database/sql-database-control-access.md) grant users the least privileges necessary.</li></ul> |
+|<br> Database Access | <ul><li>[Authentication](../../sql-database/sql-database-manage-logins.md) (Azure Active Directory Authentication) AD authentication uses identities managed by Azure Active Directory.</li><li>[Authorization](../../sql-database/sql-database-manage-logins.md) grant users the least privileges necessary.</li></ul> |
 |<br>Application Access| <ul><li>[Row level Security](https://msdn.microsoft.com/library/dn765131) (Using Security Policy, at the same time restricting row-level access  based on a user's identity,role, or execution context).</li><li>[Dynamic Data Masking](../../sql-database/sql-database-dynamic-data-masking-get-started.md) (Using Permission & Policy, limits sensitive data exposure by masking it to non-privileged users)</li></ul>|
 |**Proactive Monitoring**||  
 | <br>Tracking & Detecting| <ul><li>[Auditing](../../sql-database/sql-database-auditing.md) tracks database events and writes them to an Audit log/ Activity log in your [Azure Storage account](../../storage/common/storage-create-storage-account.md).</li><li>Track Azure Database health using [Azure Monitor Activity Logs](../../azure-monitor/platform/platform-logs-overview.md).</li><li>[Threat Detection](../../sql-database/sql-database-threat-detection.md) detects anomalous database activities indicating potential security threats to the database. </li></ul> |
-|<br>Azure Security Center| <ul><li>[Data Monitoring](../../security-center/security-center-enable-auditing-on-sql-databases.md) Use Azure Security Center as a centralized security monitoring solution for SQL and other Azure services.</li></ul>|		
+|<br>Azure Security Center| <ul><li>[Data Monitoring](../../security-center/security-center-enable-auditing-on-sql-databases.md) Use Azure Security Center as a centralized security monitoring solution for SQL and other Azure services.</li></ul>|        
 
 ## Conclusion
 Azure Database is a robust database platform, with a full range of security features that meet many organizational and regulatory compliance requirements. You can easily protect data by controlling the physical access to your data, and using a variety of options for data security at the file-, column-, or row-level with Transparent Data Encryption, Cell-Level Encryption, or Row-Level Security. Always Encrypted also enables operations against encrypted data, simplifying the process of application updates. In turn, access to auditing logs of SQL Database activity provides you with the information you need, allowing you to know how and when data is accessed.

articles/security/fundamentals/paas-applications-using-sql.md

@@ -64,7 +64,7 @@ SQL Database default source IP address restrictions allow access from any Azure
 
 To learn more about Azure SQL Firewall and IP restrictions, see:
 
-- [Azure SQL Database and SQL Data Warehouse access control](../../sql-database/sql-database-control-access.md)
+- [Azure SQL Database and SQL Data Warehouse access control](../../sql-database/sql-database-manage-logins.md)
 - [Azure SQL Database and SQL Data Warehouse firewall rules](../../sql-database/sql-database-firewall-configure.md)
 
 

articles/sql-data-warehouse/TOC.yml

@@ -94,7 +94,7 @@
     - name: Access control
       items:
       - name: Overview
-        href: ../sql-database/sql-database-control-access.md?toc=/azure/sql-data-warehouse/toc.json&bc=/azure/sql-data-warehouse/breadcrumb/toc.json
+        href: ../sql-database/sql-database-manage-logins.md?toc=/azure/sql-data-warehouse/toc.json&bc=/azure/sql-data-warehouse/breadcrumb/toc.json
       - name: Column-level security
         href: column-level-security.md
       - name: Row-level security

articles/sql-database/elastic-jobs-overview.md

@@ -29,7 +29,7 @@ If you have not used Elastic jobs, [learn more about the job automation concepts
 
 1. Create a credential for job execution in the *Job database* using [PowerShell](elastic-jobs-powershell.md) or [T-SQL](elastic-jobs-tsql.md#create-a-credential-for-job-execution).
 2. Define the target group (the databases you want to run the job against) using [PowerShell](elastic-jobs-powershell.md) or [T-SQL](elastic-jobs-tsql.md#create-a-target-group-servers).
-3. Create a job agent credential in each database the job will run [(add the user (or role) to each database in the group)](sql-database-control-access.md). For an example, see the [PowerShell tutorial](elastic-jobs-powershell.md).
+3. Create a job agent credential in each database the job will run [(add the user (or role) to each database in the group)](sql-database-manage-logins.md). For an example, see the [PowerShell tutorial](elastic-jobs-powershell.md).
 4. Create a job using [PowerShell](elastic-jobs-powershell.md) or [T-SQL](elastic-jobs-tsql.md#deploy-new-schema-to-many-databases).
 5. Add job steps using [PowerShell](elastic-jobs-powershell.md) or [T-SQL](elastic-jobs-tsql.md#deploy-new-schema-to-many-databases).
 6. Run a job using [PowerShell](elastic-jobs-powershell.md#run-the-job) or [T-SQL](elastic-jobs-tsql.md#begin-ad-hoc-execution-of-a-job).