Updates

JulianePadrao · JulianePadrao · commit 67e0b73a1da7 · 2025-02-21T16:51:53.000-06:00
diff --git a/learn-pr/wwl-data-ai/deploy-paas-solutions-with-azure-sql/includes/2-explain-paas-options-deploy-sql-server-azure.md b/learn-pr/wwl-data-ai/deploy-paas-solutions-with-azure-sql/includes/2-explain-paas-options-deploy-sql-server-azure.md
@@ -24,19 +24,19 @@ In Azure, all services support physical hardware, and you have the flexibility t
 
 ### Database Transaction Unit (DTU)
 
-[DTU-based purchasing model](/azure/azure-sql/database/service-tiers-dtu) is calculated based on a formula combining compute, storage, and I/O resources. It's a good choice for customers who want simple, preconfigured resource options.
+[DTU-based purchasing model](/azure/azure-sql/database/service-tiers-dtu?azure-portal=true) is calculated based on a formula combining compute, storage, and I/O resources. It's a good choice for customers who want simple, preconfigured resource options.
 
 The DTU purchasing model comes in several different service tiers, such as Basic, Standard, and Premium. Each tier has varying capabilities, providing a wide range of options when choosing this platform.
 
 In terms of performance, the Basic tier is used for less demanding workloads, while the Premium tier is used for intensive workload requirements.
 
 Compute and storage resources are dependent on the DTU level, and they provide a range of performance capabilities at a fixed storage limit, backup retention, and cost.
 
-For more information about DTU purchasing model, see [DTU-based purchasing model overview](/azure/azure-sql/database/service-tiers-dtu).
+For more information about DTU purchasing model, see [DTU-based purchasing model overview](/azure/azure-sql/database/service-tiers-dtu?azure-portal=true).
 
 ### vCore
 
-The [vCore-based purchasing model](/azure/azure-sql/database/service-tiers-sql-database-vcore) allows you to purchase a specified number of vCores based on your given workloads. vCore is the default purchasing model when purchasing Azure SQL Database resources. vCore databases have a specific relationship between the number of cores and the amount of memory and storage provided to the database. The vCore purchasing model is supported by both Azure SQL Database and Azure SQL Managed Instance.
+The [vCore-based purchasing model](/azure/azure-sql/database/service-tiers-sql-database-vcore?azure-portal=true) allows you to purchase a specified number of vCores based on your given workloads. vCore is the default purchasing model when purchasing Azure SQL Database resources. vCore databases have a specific relationship between the number of cores and the amount of memory and storage provided to the database. The vCore purchasing model is supported by both Azure SQL Database and Azure SQL Managed Instance.
 
 You can purchase vCore databases in three different service tiers as well:
 
@@ -50,7 +50,7 @@ The General Purpose service tier offers two compute options: **Provisioned** and
 
 ## Serverless
 
-The term "Serverless" can be misleading because you still deploy your Azure SQL Database to a logical server for connection. [Serverless](/azure/azure-sql/database/serverless-tier-overview) is a compute tier that automatically scales resources up or down based on workload demand. When the workload no longer requires compute resources, the database is paused, and only storage is billed during the inactive period. Upon a connection attempt, the database resumes and becomes available.
+The term "Serverless" can be misleading because you still deploy your Azure SQL Database to a logical server for connection. [Serverless](/azure/azure-sql/database/serverless-tier-overview?azure-portal=true) is a compute tier that automatically scales resources up or down based on workload demand. When the workload no longer requires compute resources, the database is paused, and only storage is billed during the inactive period. Upon a connection attempt, the database resumes and becomes available.
 
 :::image type="content" source="../media/module-22-plan-implement-final-24.png" alt-text="Serverless usage example for Azure SQL Database":::
 
@@ -101,16 +101,16 @@ Regardless of which restore method is implemented, it isn't possible to restore
 > [!NOTE]
 > Copy-only backup to Azure blob storage is available for SQL Managed Instance. SQL Database doesn't support this feature.
 
-For more information about automated backups, see [Automated backups - Azure SQL Database & Azure SQL Managed Instance](/azure/azure-sql/database/automated-backups-overview).
+For more information about automated backups, see [Automated backups - Azure SQL Database & Azure SQL Managed Instance](/azure/azure-sql/database/automated-backups-overview?azure-portal=true).
 
 ## Active geo-replication
 
-[Geo-replication](/azure/azure-sql/database/active-geo-replication-overview) is a business continuity feature that asynchronously replicates a database to up to four secondary replicas. As transactions are committed to the primary (and its replicas within the same region), the transactions are sent to the secondaries to be replayed. Since this communication is done asynchronously, the calling application doesn't have to wait for the secondary replica to commit the transaction before SQL Server returns control to the caller.
+[Geo-replication](/azure/azure-sql/database/active-geo-replication-overview?azure-portal=true) is a business continuity feature that asynchronously replicates a database to up to four secondary replicas. As transactions are committed to the primary (and its replicas within the same region), the transactions are sent to the secondaries to be replayed. Since this communication is done asynchronously, the calling application doesn't have to wait for the secondary replica to commit the transaction before SQL Server returns control to the caller.
 
 The secondary databases are readable and can be used to offload read-only workloads, thus freeing up resources for transactional workloads on the primary or placing data closer to your end users. Furthermore, the secondary databases can be in the same region as the primary or in another Azure region
 
 You can initiate a failover either manually by the user or programmatically by the application. If a failover occurs, you can update the application connection strings to reflect the new endpoint of what is now the primary database.
 
 ## Failover groups
 
-[Failover groups](/azure/azure-sql/database/failover-group-sql-db) are built on top of the technology used in geo-replication but provide a single endpoint for connection. The major reason for using failover groups is that they provide endpoints that can be utilized to route traffic to the appropriate replica. Your application can then connect after a failover without connection string changes.
+[Failover groups](/azure/azure-sql/database/failover-group-sql-db?azure-portal=true) are built on top of the technology used in geo-replication but provide a single endpoint for connection. The major reason for using failover groups is that they provide endpoints that can be utilized to route traffic to the appropriate replica. Your application can then connect after a failover without connection string changes.
diff --git a/learn-pr/wwl-data-ai/deploy-paas-solutions-with-azure-sql/includes/5-understand-sql-database-hyperscale.md b/learn-pr/wwl-data-ai/deploy-paas-solutions-with-azure-sql/includes/5-understand-sql-database-hyperscale.md
@@ -34,7 +34,7 @@ Security for the Hyperscale service tier offers the same robust capabilities as
     - Microsoft Entra authentication
     - Windows Authentication for Microsoft Entra principals
 
-    Azure SQL Database Hyperscale also supports [Row-Level Security (RLS)](/sql/relational-databases/security/row-level-security), allowing customers to control access to specific rows in a database table based on user characteristics, such as group membership or execution context.
+    Azure SQL Database Hyperscale also supports [Row-Level Security (RLS)](/sql/relational-databases/security/row-level-security?azure-portal=true), allowing customers to control access to specific rows in a database table based on user characteristics, such as group membership or execution context.
 
 - **Threat Protection** includes robust auditing and threat detection capabilities. SQL Database and SQL Managed Instance auditing track database activities and help maintain compliance with security standards by recording events to an audit log in a customer-owned Azure storage account. Advanced Threat Protection analyzes your logs to detect unusual behavior and potential threats to your databases. It generates alerts for suspicious activities such as SQL injection, potential data infiltration, brute force attacks, and anomalies in access patterns that can indicate privilege escalations or the use of breached credentials.
 
diff --git a/learn-pr/wwl-data-ai/deploy-paas-solutions-with-azure-sql/includes/6-examine-sql-managed-instance.md b/learn-pr/wwl-data-ai/deploy-paas-solutions-with-azure-sql/includes/6-examine-sql-managed-instance.md
@@ -1,6 +1,6 @@
 While many organizations initially migrate to Azure using IaaS offerings, the platform as a service (PaaS) provides extra benefits. With PaaS, the service handles installing and patching SQL Server, so you no longer need to perform these tasks. Consistency checks, backups, security, and performance tools are also included as part of the managed service.
 
-[Azure SQL Managed Instance](/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview) is a fully functional SQL Server instance that is nearly 100% compatible with your on-premises ecosystem. It includes features like SQL Agent, access to tempdb, cross-database queries, and common language runtime (CLR). This service uses the same infrastructure as Azure SQL Database and offers all the benefits of PaaS, such as automatic backups, automatic patching, and built-in high availability.
+[Azure SQL Managed Instance](/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview?azure-portal=true) is a fully functional SQL Server instance that is nearly 100% compatible with your on-premises ecosystem. It includes features like SQL Agent, access to tempdb, cross-database queries, and common language runtime (CLR). This service uses the same infrastructure as Azure SQL Database and offers all the benefits of PaaS, such as automatic backups, automatic patching, and built-in high availability.
 
 ### Azure SQL Managed Instance capabilities
 
@@ -16,15 +16,15 @@ Transaction log records on the primary instance can't be truncated until they're
 
 The Link feature can also be used as a hybrid disaster recovery solution, allowing you to fail over your SQL Server databases hosted anywhere to a database running on SQL Managed Instance. Additionally, you can use the Link feature to provide a read-only secondary database in SQL Managed Instance, offloading intensive read-only operations.
 
-For more information about how to configure link feature for Azure SQL Managed Instance, see [Prepare environment for link feature - Azure SQL Managed Instance](/azure/azure-sql/managed-instance/managed-instance-link-preparation).
+For more information about how to configure link feature for Azure SQL Managed Instance, see [Prepare environment for link feature - Azure SQL Managed Instance](/azure/azure-sql/managed-instance/managed-instance-link-preparation?azure-portal=true).
 
 ### Instance pool
 
 Instance pools provide a cost-efficient way to migrate smaller SQL Server instances to the cloud. Instead of consolidating smaller databases into a larger managed instance, which requires extra governance and security planning, instance pools allow you to pre-provision resources based on your total migration needs and requirements.
 
 The instance pool feature offers a fast deployment time of up to 10 minutes, making it ideal for scenarios where deployment duration is crucial. Additionally, all instances in a pool share the same virtual machine, and the total IP allocation is independent of the number of instances deployed.
 
-To learn how to deploy an instance pool for SQL Managed Instance, see [Deploy Azure SQL Managed Instance to an instance pool ](/azure/azure-sql/managed-instance/instance-pools-configure).
+To learn how to deploy an instance pool for SQL Managed Instance, see [Deploy Azure SQL Managed Instance to an instance pool ](/azure/azure-sql/managed-instance/instance-pools-configure?azure-portal=true).
 
 ### High availability and Disaster recovery
 
@@ -60,6 +60,6 @@ As with Azure SQL Database, you can't restore over an existing database. You nee
 - Backup files containing multiple backup sets can't be restored
 - Backups containing In-Memory/FILESTREAM can't be restored
 
-By default, databases in a managed instance are encrypted using [Transparent Data Encryption (TDE)](/sql/relational-databases/security/encryption/transparent-data-encryption) with a Microsoft-managed key. To take a user-initiated copy-only backup, you must disable TDE for the specific database. If a database is encrypted, you can restore it, but you need access to either the certificate or asymmetric key used for encryption. Without these, you can't restore the database to a SQL Managed Instance.
+By default, databases in a managed instance are encrypted using [Transparent Data Encryption (TDE)](/sql/relational-databases/security/encryption/transparent-data-encryption?azure-portal=true) with a Microsoft-managed key. To take a user-initiated copy-only backup, you must disable TDE for the specific database. If a database is encrypted, you can restore it, but you need access to either the certificate or asymmetric key used for encryption. Without these, you can't restore the database to a SQL Managed Instance.
 
-To learn the new features for Azure SQL Managed Instance, see [What's new in Azure SQL Managed Instance?](/azure/azure-sql/managed-instance/doc-changes-updates-release-notes-whats-new).
+To learn the new features for Azure SQL Managed Instance, see [What's new in Azure SQL Managed Instance?](/azure/azure-sql/managed-instance/doc-changes-updates-release-notes-whats-new?azure-portal=true).
