Refactor deployment and change handling descriptions for clarity and consistency across module documentation

Author: JulianePadrao

learn-pr/wwl-data-ai/integrate-sql-solutions-azure-services/5-deploy-data-api-builder-azure-services.yml

@@ -1,8 +1,8 @@
 ### YamlMime:ModuleUnit
 uid: learn.integrate-sql-solutions-azure-services.deploy-data-api-builder-azure-services
-title: Deploy Data API Builder to Azure services
+title: Explore deployment options for Data API Builder
 metadata:
-  title: Deploy Data API Builder to Azure services
+  title: Explore deployment options for Data API Builder
   description: Learn how to deploy Data API Builder to Azure Container Apps, App Service, and Static Web Apps with CI/CD automation.
   ms.date: 02/05/2026
   author: JulianePadrao

learn-pr/wwl-data-ai/integrate-sql-solutions-azure-services/7-handle-changes-event-driven-patterns.yml

@@ -3,7 +3,7 @@ uid: learn.integrate-sql-solutions-azure-services.handle-changes-event-driven-pa
 title: Handle changes with event-driven patterns
 metadata:
   title: Handle changes with event-driven patterns
-  description: Learn how to handle database changes using Change Data Capture, Change Tracking, Azure Functions SQL triggers, and Azure Logic Apps.
+  description: Learn how to handle database changes using Change Data Capture, Change Tracking, Azure Functions SQL triggers, and Change Event Streaming.
   ms.date: 02/05/2026
   author: JulianePadrao
   ms.author: jupadrao

learn-pr/wwl-data-ai/integrate-sql-solutions-azure-services/includes/1-introduction.md

@@ -9,9 +9,9 @@ In this module, you learn how to:
 - Define entities with field mappings, caching, pagination, and filtering
 - Configure REST and GraphQL endpoints for different client needs
 - Expose views, stored procedures, and define GraphQL relationships
-- Deploy Data API Builder to Azure Container Apps, App Service, or Static Web Apps
+- Explore deployment options for Data API Builder, including Azure Container Apps, App Service, and Static Web Apps
 - Set up Azure Monitor with Application Insights for API observability
-- Handle database changes using Change Data Capture, Azure Functions, and Logic Apps
+- Handle database changes using Change Data Capture, Azure Functions, and Change Event Streaming
 
 ## Prerequisites
 

learn-pr/wwl-data-ai/integrate-sql-solutions-azure-services/includes/10-summary.md

@@ -4,9 +4,9 @@ In this module, you learned how to:
 - Define entities for tables with field mappings, caching, pagination, and filtering capabilities
 - Configure REST and GraphQL endpoints with customized paths and enabled operations
 - Expose views as read-only entities and stored procedures for custom operations
-- Deploy Data API Builder to Azure Container Apps, App Service, and Static Web Apps
+- Explore deployment options for Data API Builder, including Azure Container Apps, App Service, and Static Web Apps
 - Set up Azure Monitor with Application Insights for request telemetry and database performance tracking
-- Implement change capture patterns using CDC, Change Tracking, Azure Functions triggers, and Logic Apps
+- Implement change capture patterns using CDC, Change Tracking, Azure Functions triggers, and Change Event Streaming
 
 ## Key takeaways
 

learn-pr/wwl-data-ai/integrate-sql-solutions-azure-services/includes/3-define-entities-rest-graphql.md

@@ -2,6 +2,23 @@ Entities are the core building blocks of Data API Builder. Each entity maps to a
 
 Building on the configuration file you created, the `entities` section is where you specify the tables, views, and other database objects that DAB exposes. You configure each entity with source mappings, field customizations, and relationship definitions that shape your API surface.
 
+The examples throughout this unit use the following sample database tables. Keep these definitions in mind as you work through each configuration:
+
+```sql
+CREATE TABLE dbo.Categories (
+    CategoryID INT PRIMARY KEY,
+    CategoryName NVARCHAR(50) NOT NULL
+);
+
+CREATE TABLE dbo.Products (
+    ProductID INT PRIMARY KEY,
+    ProductName NVARCHAR(100) NOT NULL,
+    UnitPrice DECIMAL(10, 2) NOT NULL,
+    UnitsInStock INT NOT NULL,
+    CategoryID INT FOREIGN KEY REFERENCES dbo.Categories(CategoryID)
+);
+```
+
 ## Map database objects to entities
 
 An entity definition starts with a name and a source reference. The entity name becomes the identifier used in API endpoints and GraphQL queries, while the source points to the actual database object.

learn-pr/wwl-data-ai/integrate-sql-solutions-azure-services/includes/7-handle-changes-event-driven-patterns.md

@@ -1,6 +1,6 @@
 Modern applications often need to respond to database changes in real time. When a customer places an order, updates their profile, or when inventory levels change, downstream systems need notification. SQL Server and Azure SQL provide several mechanisms for capturing and streaming these changes, each with different characteristics for latency, throughput, and implementation complexity.
 
-Data API Builder integrates with these change mechanisms through Azure Functions SQL trigger bindings and Azure Logic Apps connectors. Understanding when to use each approach helps you build responsive, event-driven architectures that react to data changes efficiently.
+Data API Builder integrates with these change mechanisms through Azure Functions SQL trigger bindings. Understanding when to use each approach helps you build responsive, event-driven architectures that react to data changes efficiently.
 
 ## Understand change capture mechanisms
 
@@ -115,26 +115,6 @@ Configure the connection string in your function app settings:
 > [!IMPORTANT]
 > The SQL trigger binding requires Change Tracking, not CDC. If you need CDC's historical capabilities alongside real-time triggers, enable both features on your tables.
 
-## Implement Azure Logic Apps for workflow automation
-
-[Azure Logic Apps SQL connector](/azure/connectors/connectors-create-api-sqlazure?azure-portal=true) provides low-code automation for database change scenarios. Logic Apps excel at orchestrating multi-step workflows that involve external systems like email, Teams, or other APIs.
-
-Create a Logic App that triggers when rows are modified:
-
-1. Add the **When an item is modified** trigger
-2. Configure the connection to your database
-3. Select the table to monitor
-4. Set the polling interval
-
-The trigger checks for changes at your specified interval and starts a workflow run for each modified row. Add subsequent actions to:
-
-- Send notification emails
-- Post messages to Teams channels
-- Call external APIs or webhooks
-- Update other databases or systems
-
-Logic Apps handle retry logic and error handling automatically. For complex scenarios, use parallel branches to perform multiple actions simultaneously or conditional branches to route based on data values.
-
 ## Stream changes with Change Event Streaming
 
 For high-throughput scenarios where polling latency is unacceptable, Change Event Streaming pushes changes directly to Azure Event Hubs. This approach eliminates polling delays and scales to millions of events per second.
@@ -168,22 +148,20 @@ The Event Hubs message contains:
 
 Selecting the appropriate change mechanism depends on your requirements:
 
-**Use CDC when:**
+Use **CDC** when:
+
 - You need complete before-and-after values
 - Compliance requires historical change records
 - Batch synchronization is acceptable
 
-**Use Change Tracking with Functions when:**
+Use **change tracking** with Functions when:
+
 - You need real-time response to changes
 - You only need current values, not history
 - You're building event-driven microservices
 
-**Use Azure Logic Apps when:**
-- Workflows involve multiple external systems
-- Low-code development is preferred
-- Polling latency of seconds to minutes is acceptable
+Use **change event streaming** when:
 
-**Use Change Event Streaming when:**
 - You need sub-second latency
 - High transaction volumes require streaming
 - You're building real-time analytics pipelines

learn-pr/wwl-data-ai/integrate-sql-solutions-azure-services/index.yml

@@ -18,9 +18,9 @@ abstract: |
     - Define entities for REST and GraphQL with field mappings, caching, and relationships
     - Configure REST and GraphQL endpoints with custom paths and operations
     - Expose database views, stored procedures, and GraphQL relationships
-    - Deploy Data API Builder to Azure Container Apps, App Service, or Static Web Apps
+    - Explore deployment options for Data API Builder, including Azure Container Apps, App Service, and Static Web Apps
     - Set up Azure Monitor configurations with Application Insights and Log Analytics
-    - Handle database changes using Change Data Capture, Azure Functions, and Logic Apps
+    - Handle database changes using Change Data Capture, Azure Functions, and Change Event Streaming
 prerequisites: |
   - Experience with SQL Server, Azure SQL Database, or SQL databases in Microsoft Fabric
   - Familiarity with T-SQL for creating tables, views, and stored procedures