Updates

Author: JulianePadrao

learn-pr/wwl-data-ai/configure-automatic-deployment-azure-sql-database/1-introduction.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: Introduction
   description: "Introduction"
-  ms.date: 06/28/2022
-  author: wwlpublish
+  ms.date: 02/26/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
 azureSandbox: false

learn-pr/wwl-data-ai/configure-automatic-deployment-azure-sql-database/2-describe-deployment-models-azure.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: Describe deployment models in Azure
   description: "Describe deployment models in Azure"
-  ms.date: 06/28/2022
-  author: wwlpublish
+  ms.date: 02/26/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
   ms.custom:

learn-pr/wwl-data-ai/configure-automatic-deployment-azure-sql-database/3-automate-deployment-using-azure-resource-manager-bicep.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: Automate deployment by using Azure Resource Manager templates and Bicep
   description: "Automate deployment by using Azure Resource Manager templates and Bicep"
-  ms.date: 06/28/2022
-  author: wwlpublish
+  ms.date: 02/26/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
   ms.custom:

learn-pr/wwl-data-ai/configure-automatic-deployment-azure-sql-database/4-automate-deployment-using-powershell.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: Automate deployment by using PowerShell
   description: "Automate deployment by using PowerShell"
-  ms.date: 06/28/2022
-  author: wwlpublish
+  ms.date: 02/26/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
   ms.custom:

learn-pr/wwl-data-ai/configure-automatic-deployment-azure-sql-database/5-automate-deployment-using-cli.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: Automate deployment by using Azure CLI
   description: "Automate deployment by using Azure CLI"
-  ms.date: 06/28/2022
-  author: wwlpublish
+  ms.date: 02/26/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
   ms.custom:

learn-pr/wwl-data-ai/configure-automatic-deployment-azure-sql-database/6-exercise-deploy-azure-database-using-template.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: 'Exercise: Deploy an Azure SQL Database using an Azure Resource Manager template'
   description: "Exercise: Deploy an Azure SQL Database using an Azure Resource Manager template"
-  ms.date: 06/28/2022
-  author: wwlpublish
+  ms.date: 02/26/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
   ms.custom:

learn-pr/wwl-data-ai/configure-automatic-deployment-azure-sql-database/7-knowledge-check.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: Knowledge check
   description: "Knowledge check"
-  ms.date: 06/28/2022
-  author: wwlpublish
+  ms.date: 02/26/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
 azureSandbox: false
@@ -51,7 +51,7 @@ quiz:
     - content: "apiVersion"
       isCorrect: false
       explanation: "Incorrect. ApiVersion specifics the version of the API to deploy a resource, but not dependencies."
-  - content: "Which Azure CLI command should you choose to create a SQL Database server?"
+  - content: "Which Azure CLI command should you choose to create a logical server for Azure SQL Database?"
     choices:
     - content: "az sql db op"
       isCorrect: false
@@ -61,4 +61,4 @@ quiz:
       explanation: "Correct. `az sql server create` creates a SQL Database."
     - content: "az sql db create"
       isCorrect: false
-      explanation: "Incorrect. `az sql db create` creates a database, not a SQL Database server."
+      explanation: "Incorrect. `az sql db create` creates a database, not a logical server for Azure SQL Database."

learn-pr/wwl-data-ai/configure-automatic-deployment-azure-sql-database/8-summary.yml

@@ -6,8 +6,8 @@ metadata:
   prefetch-feature-rollout: true
   title: Summary
   description: "Summary"
-  ms.date: 06/28/2022
-  author: wwlpublish
+  ms.date: 02/26/2025
+  author: JulianePadrao
   ms.author: jupadrao
   ms.topic: unit
 azureSandbox: false

learn-pr/wwl-data-ai/configure-automatic-deployment-azure-sql-database/includes/1-introduction.md

@@ -1,10 +1,12 @@
 On-premises systems require cabling and racks of hardware in order to deploy a new database server. With cloud computing, this isn't necessary. One of the major benefits of cloud computing is that system resources are abstracted behind an API. 
 
-A common term used around cloud computing deployments is *infrastructure as code*, which means all of your resources are defined a set of scripts that are stored in source control and can easily be deployed to a new environment. Although stateful resources don't need to be deployed as frequently as application code, by defining your infrastructure, you ensure that resources are implemented consistently, reducing configuration risk and human error.
+A common term in cloud computing deployments is *infrastructure as code*. This means all your resources are defined using scripts stored in source control, making it easy to deploy them to new environments. While stateful resources don't need to be deployed as often as application code, defining your infrastructure ensures consistent implementation, reducing configuration risks and human errors.
+
+Whether you're managing a single database or a complex multi-database setup, this module equips you with the skills to automate deployments efficiently and effectively.
 
 ## Learning objectives
 
-After completing this module, you will be able to:
+After completing this module, you'll be able to:
 
 - Describe the deployment models available on Azure
 - Deploy database resources using PowerShell and Azure CLI

learn-pr/wwl-data-ai/configure-automatic-deployment-azure-sql-database/includes/2-describe-deployment-models-azure.md

@@ -1,33 +1,30 @@
-Azure Resource Manager templates have the benefit of being able to deploy a full set of resources in one single declarative template. You can build dependencies into the templates, and using parameters to change deployment values at deployment time. Once you have a template, you can deploy it several ways including using an Azure DevOps pipeline, or through the custom deployments options in the Azure portal. The benefit of these deployments is that they use a declarative model, which defines what should be created. The Azure Resource Manager framework then determines how to deploy it. The alternative to the declarative model is the imperative model. Imperative frameworks include PowerShell and the Azure CLI, which follow a prescriptive order of tasks to be executed.
+Azure Resource Manager (ARM) templates allow you to deploy a complete set of resources using a single declarative template. You can define dependencies within the templates and use parameters to adjust deployment values at runtime. Once you have a template, you can deploy it in several ways, including through Azure Pipelines or the custom deployment options in the Azure portal. These deployments use a declarative model, specifying what should be created, while the ARM template framework determines how to deploy it.
 
-As mentioned above, there are two programming models that are used for cloud deployments: **imperative** and **declarative**.
-
-In **imperative** programming, you're defining a set of prescriptive tasks for the target system to execute. A simple example of this model is using a batch script to install SQL Server and its prerequisites. In **declarative** programming, you're describing a set of resources to be defined, typically by a framework. A simple example is a CREATE TABLE statement, which describes the columns and keys to be built by the SQL Server engine. The statement acts as the framework for building the table.
+In contrast, the imperative model, used by tools like PowerShell and Azure CLI, follows a specific sequence of tasks to be executed.
 
 ## Azure Resource Manager templates
 
-Azure Resource Manager templates allow you to create and deploy an entire infrastructure in a declarative framework. For example, you can deploy not only a virtual machine, but its network and storage dependencies in one document. Resource Manager also supports orchestration, which manages the deployment of interdependent resources so that they're created in the correct order. For example, a VM is dependent on the existence of a virtual network, so the framework will deploy the network (or check for the existence of the network) before attempting to build the VM. Azure Resource Manager templates also support extensibility, which allows you to run PowerShell or Bash scripts on your resources after they're deployed.
+[Azure Resource Manager](/azure/azure-resource-manager/management/overview) templates enable you to create and deploy an entire infrastructure in a declarative manner. For instance, you can deploy a virtual machine along with its network and storage dependencies in one document. ARM template supports orchestration, managing the deployment of interdependent resources in the correct order. ARM templates also support extensibility, allowing you to run PowerShell or Bash scripts on your resources post-deployment.
 
 ## PowerShell
 
-PowerShell provides a core module known as Az PowerShell module, which has child resource providers for nearly all Azure services. For example, **Az.Compute** would cover Azure Virtual Machines. PowerShell is more commonly used for resource modification and status retrieval. While it's possible to create resources using PowerShell, it isn't typically used for complex deployments. PowerShell can also be used to deploy Azure Resource Manager templates, so in a sense it supports both declarative and imperative models.
+[PowerShell](/powershell/scripting/overview), with its Az module, provides cmdlets for nearly all Azure services. For example, **Az.Compute** covers Azure Virtual Machines. PowerShell is often used for resource modification and status retrieval. While it can create resources, it isn't typically used for complex deployments. PowerShell can also deploy ARM templates, supporting both declarative and imperative models.
 
 ## Azure CLI
 
-The Azure Command Line Interface, or CLI, is similar to PowerShell in that it can be used either imperatively or declaratively. Much like PowerShell and Azure Resource Manager templates, the Azure CLI provides a mechanism to deploy or modify Azure Resources. Some commands for Azure PostgreSQL and Azure MySQL Databases are only available in the Azure CLI.
+[Azure Command-Line Interface (CLI)](/cli/azure/what-is-azure-cli) is similar to PowerShell, supporting both imperative and declarative operations. The Azure CLI can deploy or modify Azure resources, and some commands for Azure PostgreSQL and Azure MySQL Databases are exclusive to the CLI.
 
 ## Azure portal
 
-The Azure portal is a graphical interface to Azure Resource Manager. Any resources you build and deploy using the portal will have an Azure Resource Manager template that you can capture by selecting **Export template** in the **Overview** section of your resource group.
+The Azure portal is a graphical interface for ARM template. Any resources you create and deploy using the portal will have an ARM template that you can export by selecting **Export template** in the **Automation** section of your resource group.
 
-:::image type="content" source="../media/module-66-automation-final-01.png" alt-text="Screenshot of the export template option on resource group on Azure portal." lightbox="../media/module-66-automation-final-01.png":::
+:::image type="content" source="../media/module-66-automation-final-01.png" alt-text="Screenshot of the export template option on the resource group blade from Azure portal." lightbox="../media/module-66-automation-final-01.png":::
 
-The Azure portal is usually the easiest way to get started when first learning about the Azure platform. Organizations (and DBAs) typically move into a more automated model of deployment as their Azure estate and experience grows.
+The Azure portal is often the easiest way to get started with Azure. As organizations and DBAs gain experience, they typically move to more automated deployment models.
 
-## Azure DevOps
+## Azure DevOps Services
 
-In Azure DevOps, deployments are carried out using Azure Pipelines. Azure Pipelines are a fully featured continuous integration and continuous delivery service (CI/CD), which allows you to automate the build, testing, and deployment of your code. You can deploy Azure resources using Azure Resource Manager templates in two ways... The first method calls a PowerShell script as shown above. The second approach defines tasks that stage your artifacts (the templates themselves and any required secrets) and then deploys the templates. One task stages the artifacts and the other tasks deploys the templates.
+In Azure DevOps Services, deployments are managed using Azure Pipelines, a comprehensive CI/CD service that automates the build, testing, and deployment of your code. You can deploy Azure resources using ARM templates in two ways: by calling a PowerShell script or by defining tasks that stage your artifacts (templates and required secrets) and then deploy the templates. This automation ensures that your deployments are consistent and reliable, reducing the risk of human error.
 
-## Continuous integration
+Continuous integration (CI) complements this by focusing on making small, frequent changes to code and regularly checking it into a version control system. CI automates the build, packaging, and testing of applications, facilitating better collaboration among developers and improving code quality. Continuous delivery (CD) builds on CI by automating the delivery of code changes to the underlying infrastructure, ensuring that your deployments aren't only consistent but also rapid and efficient. Together, Azure Pipelines and CI/CD practices streamline the entire development and deployment process, making it more efficient and reliable.
 
-Continuous integration is a development methodology that focused on making small changes to code and frequent code check-ins to the version control system. Continuous integration provides an automated way to build, package, and test applications. Having the framework in place facilitates more frequent check-ins, and allows better collaboration between developers, with the goal of improving code quality. Continuous delivery builds on the continuous integration and automates the delivery of code changes to the underlying infrastructure.